![Introducing Enhanced Alert Actions and Triage Functionality](https://cdn.sanity.io/images/cgdhsj6q/production/fe71306d515f85de6139b46745ea7180362324f0-2530x946.png?w=800&fit=max&auto=format)
Product
Introducing Enhanced Alert Actions and Triage Functionality
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
@clabs/packages-publisher
Advanced tools
Readme
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 @clabs/packages-publisher
You can check it has been installed by running:
packages-publisher --help
or the short version:
pkgs --help
This tool should be ran from the root of the monorepo for multiple packages. It can also be ran from within a single package. It can either be ran directly or added to your npm scripts.
Note that if you are using yarn
you might need to add a .yarnrc
with npm's registry so that it can find the right information when publishing. See this package's .yarnrc
for an example.
You need to indicate what's the path where packages can be found. For that, you can add a configuration to the package.json at the root of your monorepo.
{
[...]
"pkgs": {
"path": "./packages"
}
[...]
}
Alternatively, if path is not configured there, you can pass it as a flag to the commands.
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
The npm package @clabs/packages-publisher receives a total of 0 weekly downloads. As such, @clabs/packages-publisher popularity was classified as not popular.
We found that @clabs/packages-publisher demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 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.
Product
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
Security News
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
Security News
OpenSSF is warning open source maintainers to stay vigilant against reputation farming on GitHub, where users artificially inflate their status by manipulating interactions on closed issues and PRs.