Releases and channels for the Snyk CLI

This page describes Snyk CLI releases and channels, and also explains how to opt-in to a channel from the IDE.

Releases

Beginning with v.1.1291.0, the Snyk CLI follows the industry standard Semantic Versioning three-part notation as follows.

Given a version number MAJOR.MINOR.PATCH, increment the:

  1. MAJOR version when you make [breaking] changes

  2. MINOR version when you add functionality in a backward-compatible manner

  3. PATCH version when you make backward-compatible bug fixes

Additional labels are added for CLI releases as needed based on the standard.

In the Snyk CLI context, Snyk defines a breaking change as a change that could break automated workflows and cause failures in your existing working setup, such as CI/CD integrations. Breaking changes will be indicated by incrementing MAJOR and mentioned in the release notes too.

Some examples of breaking changes are the following:

  • Deprecating or changing output fields, field names, or environment variables

  • Introducing mandatory configuration changes

  • Changes in error or exit codes

Channels

Beginning with v.1.1291.0, Snyk is providing different channels to enable customers to opt-in to a channel based on their needs and preferences.

When you select a channel, you are selecting the stability level you want to use: preview, rc, or stable.

preview

Snyk offers a preview channel for those who want to test in-progress features. However, keep in mind that this channel may contain bugs and is not officially supported.

A preview version is not recommended for production environments. It may contain bugs and is best tested in a local environment. For instructions on installing a preview version, see Install standalone executables from a channel.

rc

  • Release candidate: pre-releases are deployed at distinct points in time and contain a version of the CLI that is expected to be promoted to stable after additional testing.

  • Version Pattern: v{MAJOR}.{MINOR}.{PATCH}-rc

  • Cadence: every eight weeks, two weeks before a stable release (hotfix releases possible)

stable

Snyk recommends opting in to a stable channel for the following reasons:

  • A stable build is tested extensively over the course of eight weeks during which Snyk development teams use the CLI in the SDLC process

  • Accompanying release notes help you decide which version best suits your needs

However, customers who would like to receive code changes as soon they are merged can opt in to the preview channel. Note that Snyk does not offer support for the preview channel and expects known issues to be present in this channel.

Existing Snyk customers who are opted in to the previously known latest channel will be automatically opted in to the stable channel. Snyk is mirroring the latest channel and the stable channel to avoid disruption to existing customers. However, Snyk encourages you to switch to the new channels as shown above.

Install standalone executables from a channel

Use therelease.json in each channel. The download links are provided here, followed by an example for the preview version on the MacOS platform:

For MacOS, download and run a preview version of the CLI in a temporary folder named snyk-preview. To do this, you can run the following set of commands.

mkdir snyk-preview
cd snyk-preview
curl --compressed https://downloads.snyk.io/cli/preview/snyk-macos -o snyk
chmod +x ./snyk
./snyk -version

Selecting a channel from the IDE

This functionality is available in the IntelliJ IDE. Snyk is extending this capability to other supported IDEs.

The default channel for all IDEs is the stable channel.

To select a channel from the IDE, choose a CLI release channel using the dropdown, as shown in the screenshot that follows. Users can switch between channels, for example, switch to release-candidate (rc) to receive a hotfix.

However, Snyk also recommends the stable channel as the default for IDE users.

Last updated

More information

Snyk privacy policy

© 2024 Snyk Limited | All product and company names and logos are trademarks of their respective owners.