Introducing Semantic Versioning, and Release Channels to Snyk CLI

We are pleased to introduce Semantic Versioning and Release Channels to Snyk CLI from v.1.1291.0 onwards. These changes will allow all Snyk customers to select a sustainable release cadence that works for them, and help optimize governance and compliance overhead for enterprise customers.

Snyk CLI v.1.1291.0 follows three part MAJOR.MINOR.PATCH notation going forward, details for which are available in product documentation.

We are introducing the following release channels:

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:

  • https://static.snyk.io/cli/preview/

  • https://static.snyk.io/fips/cli/preview/

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 8 weeks, 2 weeks before a stable release (hotfix releases possible)

• Availability:

  • https://static.snyk.io/cli/rc/

  • https://static.snyk.io/fips/cli/rc/

stable stable builds are deployed at distinct points in time after being additionally tested and considered stable.

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

• Cadence: every 8 weeks, end of an even month (hotfix releases possible)

• Availability:

  • https://github.com/snyk/cli/releases/

  • https://static.snyk.io/cli/stable/

  • https://static.snyk.io/fips/cli/stable/

  • npm

  • brew

  • scoop

  • Snyk-images

Existing Snyk CLI, and supported IDEs users are opted into the stable channel by default. You can find more information on how to opt into a release channel of your choice in our product documentation.