Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade @snyk/protect from 1.1292.4 to 1.1293.0 #660

Merged
merged 1 commit into from
Sep 19, 2024

Conversation

jesperancinha
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade @snyk/protect from 1.1292.4 to 1.1293.0.

ℹ️ 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 1 version ahead of your current version.

  • The recommended version was released on 22 days ago.

Release notes
Package name: @snyk/protect
  • 1.1293.0 - 2024-08-28

    1.1293.0 (2024-08-28)

    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

    • Starting with this version, Snyk cli binaries will be distributed via downloads.snyk.io instead of static.snyk.io. This includes intallation from npm, homebrew and scoop as well as many of the CI/CD integrations.

    Features

    • sbom: add support for license issues in sbom test (6948668)
    • auth: Use OAuth2 as default authentication mechanism (35949c4)
    • config: Introduce config environment command (0d8dd2b)
    • container: When docker is not installed, platform parameter is now supported (64b405d)

    Bug Fixes

    • auth: align auth failure error messages for oauth (e3bfec3)
    • auth: ensure environment variable precedence for auth tokens (24417d6)
    • test: fix a bug related to multi-project .NET folder structures (755a38f)
    • test: multiple pnpm workspace improvements (da5c14f)
    • test: fixes a bug regarding Snyk attempting to get the dependencies from the wrong nuget *.deps.json file.(2e17434)
    • test: support for pipenv with python 3.12 (09df3bc)
    • test: support multi-part comparison for python pip versions. (b625eb9)
    • container: container monitor with --json now outputs valid json(039c9bd)
    • container: support hashing large .jar files (6f82231)
    • sbom: fix issues in JSON output of sbom test command, include CWE values on CWE property (#5331) (99773c3)
    • sbom: include all detected dep-graphs of a container image (ea43977)
    • iac: fixed an issue where the resource path was missing for certain Terraform resources. IAC-3015
    • general: map previously unhandled exit codes to exit code 2 (9fde4fe)
    • general: use entitlements when signing bundled macos binaries (bebc59c)
  • 1.1292.4 - 2024-08-12

    1.1292.4 (2024-08-12)

    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

    • deployment: Rollback of digital signature for the bundled macOS binary (#5416)
from @snyk/protect GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

Snyk has created this PR to upgrade @snyk/protect from 1.1292.4 to 1.1293.0.

See this package in npm:
@snyk/protect

See this project in Snyk:
https://app.snyk.io/org/jesperancinha-github-marketplace/project/57381669-0e69-4180-8b56-9a55abe8d9a7?utm_source=github&utm_medium=referral&page=upgrade-pr
@jesperancinha jesperancinha merged commit 2694cee into gomix Sep 19, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants