@myparcel/semantic-release-config
Advanced tools
This package contains multiple semantic-release presets. Additional information, documentation and guides on semantic-release can be found on https://eslint.org/
Install the package via 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/github
FAQs
Reusable configurations for semantic-release
The npm package @myparcel/semantic-release-config receives a total of 22 weekly downloads. As such, @myparcel/semantic-release-config popularity was classified as not popular.
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
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
Security News
A Stanford study reveals 9.5% of engineers contribute almost nothing, costing tech $90B annually, with remote work fueling the rise of "ghost engineers."