Releases and channels for the Snyk CLI
This page describes Snyk CLI releases and support policy, and also explains how to opt-in to different channels and the purpose of each channel.
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:
MAJOR version when you make [breaking] changes
MINOR version when you add functionality in a backward-compatible manner
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
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.
Preview: pre-release builds are deployed regularly up to multiple times a day and contain the latest changes.
Version Pattern: v{MAJOR}.{MINOR}.{PATCH}-preview
Cadence: Varying
Availability:
Alpine arm64: https://downloads.snyk.io/cli/preview/snyk-alpine-arm64
For fips, add
fipsto the base URL, for example,https://downloads.snyk.io/fips/cli/preview/snyk-linux
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)
Availability:
MacOS arm64: https://downloads.snyk.io/cli/rc/snyk-macos-arm64
Linux arm64: https://downloads.snyk.io/cli/rc/snyk-linux-arm64
Alpine arm64: https://downloads.snyk.io/cli/rc/snyk-alpine-arm64
For fips, add
fipsto the base URL, for example,https://downloads.snyk.io/fips/cli/rc/snyk-linux
stable
Stable: builds are deployed at distinct points in time after additional testing and are considered stable.
Version Pattern: v{MAJOR}.{MINOR}.{PATCH}
Cadence: every eight weeks (hotfix releases possible)
Availability:
Alpine arm64: https://downloads.snyk.io/cli/stable/snyk-alpine-arm64
For fips, add
fipsto the base URL, for example,https://downloads.snyk.io/fips/cli/stable/snyk-linux
Installation methods:
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.
Support policy
Snyk supports the latest 12 months of CLI versions in the stable channel, ensuring functionality and performance. Older versions are considered End-of-Support (EOS) and will not receive bug fixes or support for troubleshooting.
Snyk provides fixes only in new versions and cannot fix older versions. Customers must upgrade to benefit from improvements.
This policy fosters innovation while optimizing resources.
If you need help, submit a request to Snyk Support.
Runtime requirements
This section specifies the minimum requirements for the latest CLI, covering aspects such as the operating system, dynamically linked libraries, and runtimes.
Snyk CLI is designed and expected to run on operating system environments that are actively supported by their vendors and have not reached their End of Support (EOS) or End of Life (EOL). Once an operating system environment reaches its end of support, Snyk will cease testing and providing support for Snyk CLI in that specific environment.
macOS
10.13
10.13
Linux
glibc ≥ 2.28 & OpenSSL ≥ 3.0 (Enterprise Linux 8, Ubuntu 20.04, Debian buster, other distros)
glibc ≥ 2.31 & OpenSSL ≥ 3.0
(Enterprise Linux 9, Ubuntu 20.04, Debian bullseye, other distros)
Alpine
musl libc >= 1.1.18 (3.7.3, other distros)
musl libc >= 1.1.18 (3.7.3, other distros)
Windows
8.1
-
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 -versionSelecting a channel from the IDE
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
Was this helpful?