some-publisher
Advanced tools
CLI for publishing packages within a repository using the same version for all packages
Tool to help publishing packages within a repository, using the same version for all packages.
You can install it globally to use across projects:
npm install -g packages-publisher
You can check it has been installed by running:
packages-publisher --help
or the short version:
pkgs --help
At any point, you can run pkgs [command] --help to learn more about a command.
This bumps all packages in the given path and where they are used as dependencies as well.
Example:
pkgs bump-versions minor --path packages
Builds and publishes all packages in the given path to npm. You can skip build if you have a monorepo build type.
Example:
pkgs publish --path packages [--otp 123456] [--skip-build]
FAQs
CLI for publishing packages within a repository using the same version for all packages
We found that some-publisher demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.