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

build(deps): bump github.com/sigstore/sigstore-go from 0.5.1 to 0.6.1 in /example in the go_modules group across 1 directory #3427

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

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 9, 2025

Bumps the go_modules group with 1 update in the /example directory: github.com/sigstore/sigstore-go.

Updates github.com/sigstore/sigstore-go from 0.5.1 to 0.6.1

Release notes

Sourced from github.com/sigstore/sigstore-go's releases.

v0.6.1

What's Changed

v0.6.1 resolves a security advisory for a denial of service. See GHSA-cq38-jh5f-37mq for more information.

Full Changelog: sigstore/sigstore-go@v0.6.0...v0.6.1

v0.6.0

As folks use sigstore-go in more cases, we continue to make fixes and do some minor API interface changes.

Because we are pre-1.0.0 these were made as breaking changes. After 1.0.0 we will provide deprecation notices and smoother migration paths. There may be more minor interface changes between now and v1.0.0.

Breaking Changes

  • In pkg/bundle/bundle.go
    • ProtobufBundle is now Bundle
    • NewProtobufBundle is now NewBundle
  • In pkg/bundle/signature_content.go
    • Use Statement() type was from github.com/in-toto/in-toto-golang/in_toto now comes from github.com/in-toto/attestation/go/v1

What's Changed

Full Changelog: sigstore/sigstore-go@v0.5.1...v0.6.0

Commits
  • 01e70e8 Add hard limits for number of TSA entries, Tlog entries, and attestation subj...
  • e50c2d7 Add additional validation for nil elements in Bundles (#285)
  • 725e508 Fix proof of key possession generation (#283)
  • ca85ca5 Bump github/codeql-action from 3.26.5 to 3.26.6 (#284)
  • 79a4e82 Bump github/codeql-action from 3.26.2 to 3.26.5 (#281)
  • c91d45f add oss-fuzz build script (#278)
  • 2198ac3 Add the ability to contruct TrustRoot from targets (#247)
  • f9235ff Add fuzz tests for bundle, tlog and verify packages (#272)
  • 1bcaee1 Bump github/codeql-action from 3.26.0 to 3.26.2 (#275)
  • 3f8dbc4 Bump golang.org/x/mod from 0.19.0 to 0.20.0 (#255)
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Jan 9, 2025
@gmlewis
Copy link
Collaborator

gmlewis commented Jan 9, 2025

@dnwe - what do you recommend as the best option for fixing this alert?

@dnwe
Copy link
Contributor

dnwe commented Jan 9, 2025

@dnwe - what do you recommend as the best option for fixing this alert?

Yeah this is GO-2024-3116 — in its current state we cannot pickup the fix. Need to help sigstore to sort out their directives to be more permissive so that people can upgrade to resolve this vuln, but there have a few dependent repos that need fixing before sigstore-go itself can be fixed.

@gmlewis gmlewis added the DO NOT MERGE Do not merge this PR. label Jan 9, 2025
@dependabot dependabot bot force-pushed the dependabot/go_modules/example/go_modules-909bd1a915 branch from 97ff49a to 21e30ea Compare February 5, 2025 14:38
@dnwe
Copy link
Contributor

dnwe commented Feb 5, 2025

@gmlewis this should be solvable now, as I worked with sigstore to adopt a similar stance on their go.mod files, and the PR diff looks good, but seems like CI checks are failing at the moment. We need to investigate what changes are needed in those

@gmlewis
Copy link
Collaborator

gmlewis commented Feb 5, 2025

@dependabot recreate

@gmlewis gmlewis removed the DO NOT MERGE Do not merge this PR. label Feb 5, 2025
Bumps the go_modules group with 1 update in the /example directory: [github.com/sigstore/sigstore-go](https://github.com/sigstore/sigstore-go).


Updates `github.com/sigstore/sigstore-go` from 0.5.1 to 0.6.1
- [Release notes](https://github.com/sigstore/sigstore-go/releases)
- [Commits](sigstore/sigstore-go@v0.5.1...v0.6.1)

---
updated-dependencies:
- dependency-name: github.com/sigstore/sigstore-go
  dependency-type: direct:production
  dependency-group: go_modules
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/go_modules/example/go_modules-909bd1a915 branch from 21e30ea to baa1853 Compare February 5, 2025 17:47
@gmlewis
Copy link
Collaborator

gmlewis commented Feb 5, 2025

@gmlewis this should be solvable now, as I worked with sigstore to adopt a similar stance on their go.mod files, and the PR diff looks good, but seems like CI checks are failing at the moment. We need to investigate what changes are needed in those

@dnwe - I'm still having troubles with this one. I also tried manually creating a PR that bumps the dependency, but still came across the same toolchain issues as before.

If you can create a PR that replaces this one, I'm fine with that as well.

@gmlewis gmlewis added the DO NOT MERGE Do not merge this PR. label Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file DO NOT MERGE Do not merge this PR. go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants