@myparcel/semantic-release-config
Advanced tools
This package contains multiple semantic-release presets. Additional information, documentation and guides on semantic-release can be found here
Install the package via yarn:
yarn add -D @myparcel/semantic-release-config
or npm:
npm i -D @myparcel/semantic-release-config
Create a semantic-release config file, if you haven't already, and add the following: (JavaScript example)
// release.config.js
module.exports = {
extends: '@myparcel/semantic-release-config',
};
Or to use one of the other available presets:
// release.config.js
module.exports = {
extends: '@myparcel/semantic-release-config/npm',
};
@myparcel/semantic-release-config
This is the base configuration, which other ones should be based on. For more in-depth information on the configurations
used with each plugin, see ./src/plugins/<plugin>.js.
@myparcel/semantic-release-config/npm
@myparcel/semantic-release-config/npm
@myparcel/semantic-release-config/github
@myparcel/semantic-release-config/github-composer
@myparcel/semantic-release-config/github-npm
You can run the following command in your project to test your semantic-release configuration:
npx semantic-release --dry-run --debug --branches=$(git branch --show-current)
Flags used:
--dry-run: If this is on, no files are changed and nothing is actually "released".--debug: Enables debug mode to show a lot more output.--branches: Set the current branch as a release branch. If you don't pass this and are not on a release branch
semantic-release will not process your commits.FAQs
Reusable configurations for semantic-release
We found that @myparcel/semantic-release-config demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.