Skip to content

[Snyk] Upgrade sigstore from 1.5.2 to 1.9.0 #26

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

X-oss-byte
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade sigstore from 1.5.2 to 1.9.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 4 versions ahead of your current version.
  • The recommended version was released 6 months ago, on 2023-08-10.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
417/1000
Why? Proof of Concept exploit, CVSS 6.2
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Release notes
Package name: sigstore
  • 1.9.0 - 2023-08-10
  • 1.8.0 - 2023-07-19
  • 1.7.0 - 2023-06-30
  • 1.6.0 - 2023-06-06
  • 1.5.2 - 2023-05-16
from sigstore GitHub release notes
Commit messages
Package name: sigstore

Compare


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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link

changeset-bot bot commented Jan 26, 2024

⚠️ No Changeset found

Latest commit: 54db03e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Type: Enhancement

PR Summary: The pull request upgrades the 'sigstore' dependency from version 1.5.2 to 1.9.0 to address known vulnerabilities and keep the dependencies up-to-date.

Decision: Comment

📝 Type: 'Enhancement' - not supported yet.
  • Sourcery currently only approves 'Typo fix' PRs.
✅ Issue addressed: this change correctly addresses the issue or implements the desired feature.
No details provided.
📝 Complexity: the changes are too large or complex for Sourcery to approve.
  • Unsupported files: the diff contains files that Sourcery does not currently support during reviews.

General suggestions:

  • Ensure that the upgrade of the 'sigstore' dependency is thoroughly tested, especially since it jumps multiple versions which might include breaking changes or new features that could affect the existing codebase.
  • Verify that the rest of the codebase is compatible with the new version of 'sigstore', and make any necessary adjustments to the code where the 'sigstore' API has changed.
  • Review the release notes and commit messages provided by Snyk to understand the changes introduced in the new version of 'sigstore' and how they might impact the application.

Thanks for using Sourcery. We offer it for free for open source projects and would be very grateful if you could help us grow. If you like it, would you consider sharing Sourcery on your favourite social media? ✨

Share Sourcery

Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.

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