Added support for read-only tokens
Bytesafe now supports read-only tokens. For example, these can be used in CI/CD pipelines where you only require read access or similar use cases.
Read moreBytesafe now supports read-only tokens. For example, these can be used in CI/CD pipelines where you only require read access or similar use cases.
Read moreThe Teams plan enables teams management, basic access control, Slack integration and full access to all our plugins and policies.
Read moreThe release brings Security Scanning features to Bytesafe registries, by adding a Vulnerability Scanner plugin and three security related policies.
We are also releasing a Slack integration which allows you to be notified when new vulnerabilities are found in your account.
Read moreTwo main features of the release related to release management: Promote functionality for package versions as well as Version auto increment plugin has been added.
Promote package, lets you select a existing package version and promote it to a new version (and possible new target registry), removing the need to re-publish from your project and running the risk of including unplanned changes.
Read moreThe npm deprecate command is now supported with Bytesafe registries.
Additionally, deprecate information linked to the package version is now available as output when using npm install and bytesafe push / pull.
Information regarding deprecated package versions is also available in the Bytesafe web console.
Read moreMain feature added by the release is a Bytesafe CLI for the Windows OS. Windows CLI is available for download from the CLI page in the Bytesafe web console.
Release notes:
npm whoami, ping, audit, logout, token commandsyarn commandsWe are happy to introduce Policies & Plugins for Bytesafe registries:
The main feature of the initial release is to provide private registry functionality, including: