publish manager for multiple registry (jsr, npm and private registries)
MIT License
npm i -g pubm
Usage:
$ pubm [version]
Version can be:
major | premajor | minor | preminor | patch | prepatch | prerelease | 1.2.3
Options:
--test-script <script> The npm script to run tests before publishing (default: test)
--build-script <script> The npm script to run build before publishing (default: build)
-p, --preview Show tasks without actually executing publish
-b, --branch <name> Name of the release branch (default: main)
-a, --any-branch Show tasks without actually executing publish
--no-pre-check Skip prerequisites check task
--no-condition-check Skip required conditions check task
--no-tests Skip running tests before publishing
--no-build Skip build before publishing
--no-publish Skip publishing task
--no-release-draft Skip creating a GitHub release draft
--publish-only Run only publish task for latest tag
-t, --tag <name> Publish under a specific dist-tag (default: latest)
-c, --contents <path> Subdirectory to publish
--no-save-token Do not save jsr tokens (request the token each time)
--registry <...registries> Target registries for publish
registry can be npm | jsr | https://url.for.private-registries (default: npm,jsr)
-h, --help Display this message
-v, --version Display version number
You can have either package.json or jsr.json.
pubm.js
or pubm.mjs
The only way to access jsrs certified environment is through a direct API request with a token.
The jsr token is encrypted and stored using various layers of information. As long as you have control over the local machine where pubm was run, it is highly unlikely the token can be compromised.
If you prefer not to save tokens, you can use the --no-save-token
option, which will request the token each time.