Snyk has created this PR to upgrade @snyk/protect from 1.1269.0 to 1.1292.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 34 versions ahead of your current version.
The recommended version was released on a month ago.
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Complete changelog
Bug Fixes
test,monitor: fix improper permission error handling when accessing 'enablePnpmCli' feature flag
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
News
This Snyk CLI release delivers an assortment of bug fixes and improvements.
We've added support for pnpm, giving you more flexibility in your project setup.
You can now scan npm/yarn projects even without lockfiles, ensuring comprehensive vulnerability detection regardless of your dependency management approach.
We're committed to strengthening security. This release includes redaction of additional sensitive data in debug logs, minimizing potential risks.
Complete changelog
Features
test: Added pnpm support under 'enablePnpmCli' feature flag (#5181) (46769cc)
test: Support scan of npm/yarn projects without lockfiles (e2d77a9)
monitor: Set target-reference in the monitor request (51ed8f5)
code: Centrally check if code test is enabled (#5239) (e5a00e2)
sbom: Improve depgraph for Maven projects (fbb33d7)
sbom: Use RFC 3339 for all timestamps in sbom test result (#5204) (91bf191)
language-server: Add --all-projects flag scans by default IDE-318 (fdcf30e)
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Bug Fixes
dependencies: Upgrade go-getter to v1.7.4 to fix vulnerabilities (#5252)
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
News
This is the first stable release of the CLI
It makes use of semantic versioning and is the successor of 1.1290.0
Bug Fixes
test: Fix support of cyclic dependencies in maven with dverbose #5208
Snyk has created this PR to upgrade @snyk/protect from 1.1269.0 to 1.1292.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 34 versions ahead of your current version.
The recommended version was released on a month ago.
Release notes
Package name: @snyk/protect
1.1292.1 (2024-06-27)
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Complete changelog
Bug Fixes
1.1292.0 (2024-06-26)
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
News
This Snyk CLI release delivers an assortment of bug fixes and improvements.
Complete changelog
Features
Bug Fixes
1.1291.1 (2024-05-27)
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
Bug Fixes
1.1291.0 (2024-04-30)
The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation
News
Bug Fixes
1.1290.0 (2024-04-18)
Bug Fixes
Features
1.1289.0 (2024-04-16)
Bug Fixes
Features
1.1288.1 (2024-04-15)
Bug Fixes
1.1288.0 (2024-04-09)
Bug Fixes
Features
1.1287.0 (2024-04-04)
Features
1.1286.4 (2024-04-04)
Bug Fixes
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: