
Security News
Deno 2.2 Improves Dependency Management and Expands Node.js Compatibility
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.
@amanda-mitchell/semantic-release-npm-multiple
Advanced tools
A semantic release plugin to publish an NPM package to multiple registries.
This is a thin wrapper around the @semantic-release/npm plugin for Semantic Release that allows it to be called multiple times, which can be useful if you need to publish to multiple NPM registries simultaneously.
yarn add --dev @amanda-mitchell/semantic-release-npm-multiple
The plugin can be configured in the semantic-release configuration file:
{
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
[
"@amanda-mitchell/semantic-release-npm-multiple",
{
"registries": {
"registryName1": {
"npmPublish": true
},
"registryName2": {
"npmPublish": true
}
}
}
]
]
}
Each of the keys in registries
refers to a specific registry that should be used and may be any value that is meaningful to you.
The object associated with that key is a set of options that should be passed to the @semantic-release/npm
plugin when calling it.
@amanda-mitchell/semantic-release-npm-multiple
also looks at a number of environment variables for its configuration:
NPM_TOKEN
NPM_USERNAME
NPM_PASSWORD
NPM_EMAIL
NPM_CONFIG_REGISTRY
NPM_CONFIG_USERCONFIG
For any of these variables, if you define a {UPPER_CASE_REGISTRY_NAME}_{VARIABLE}
environment variable, it will be used instead.
For example, if you wanted to publish a package to both a GitHub private registry and the public NPM registry, you would first create a configuration file like this:
{
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
[
"@amanda-mitchell/semantic-release-npm-multiple",
{
"registries": {
"github": {},
"public": {}
}
}
]
]
}
And then, when running semantic-release
, set these environment variables:
GITHUB_NPM_CONFIG_REGISTRY=https://npm.pkg.github.com/
GITHUB_NPM_TOKEN=XXXXX
PUBLIC_NPM_CONFIG_REGISTRY=https://registry.npmjs.org
PUBLIC_NPM_TOKEN=XXXXX
FAQs
A semantic release plugin to publish an NPM package to multiple registries.
The npm package @amanda-mitchell/semantic-release-npm-multiple receives a total of 2,786 weekly downloads. As such, @amanda-mitchell/semantic-release-npm-multiple popularity was classified as popular.
We found that @amanda-mitchell/semantic-release-npm-multiple demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.
Security News
React's CRA deprecation announcement sparked community criticism over framework recommendations, leading to quick updates acknowledging build tools like Vite as valid alternatives.
Security News
Ransomware payment rates hit an all-time low in 2024 as law enforcement crackdowns, stronger defenses, and shifting policies make attacks riskier and less profitable.