chore(deps): bump github.com/sigstore/sigstore-go from 1.1.3 to 1.1.4 #12299
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4c01930 to
cb87d8f
Compare
Bumps [github.com/sigstore/sigstore-go](https://github.com/sigstore/sigstore-go) from 1.1.3 to 1.1.4. - [Release notes](https://github.com/sigstore/sigstore-go/releases) - [Commits](sigstore/sigstore-go@v1.1.3...v1.1.4) --- updated-dependencies: - dependency-name: github.com/sigstore/sigstore-go dependency-version: 1.1.4 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
cb87d8f to
9fc6c06
Compare
jpoley
added a commit
to jpoley/flowspec
that referenced
this pull request
Dec 16, 2025
…022-25883 This PR applies REAL fixes for Docker image vulnerabilities, unlike PRs 887-896 which were assumption-based and fixed nothing. Security Fixes: - CVE-2025-64756 (glob@11.0.3): FIXED by removing npm from final image npm is only used during build to install pnpm, then removed via apk del - CVE-2022-25883 (semver@7.0.0): FIXED by removing @githubnext/github-copilot-cli Root cause: copilot-cli -> simple-update-notifier@1.1.0 -> semver@~7.0.0 Upstream issue open since Sep 2024, maintainer unresponsive - CVE-2025-66564 (sigstore/timestamp-authority): RISK ACCEPTED gh CLI has this compiled in, awaiting cli/cli PR #12299 to fix Memory exhaustion vuln requires attacker-controlled timestamp server Changes: - Dockerfile: Remove npm after pnpm install, remove copilot-cli - Added vulnerability-tracking.jsonl for CVE tracking with upstream issues - Added DOCKER_SCOUT_POLICY.md with manual policy configuration steps Upstream Issues Tracked: - npm/cli#8741 (glob) - CLOSED but unfixed - cli/cli#12299 (sigstore) - OPEN PR - alexbrazier/simple-update-notifier#30 (semver) - OPEN, no response 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: jason poley <jason.poley@gmail.com>
Closed
5 tasks
jpoley
added a commit
to jpoley/flowspec
that referenced
this pull request
Dec 16, 2025
…022-25883 This PR applies REAL fixes for Docker image vulnerabilities, unlike PRs 887-896 which were assumption-based and fixed nothing. Security Fixes: - CVE-2025-64756 (glob@11.0.3): FIXED by removing npm from final image npm is only used during build to install pnpm, then removed via apk del - CVE-2022-25883 (semver@7.0.0): FIXED by removing @githubnext/github-copilot-cli Root cause: copilot-cli -> simple-update-notifier@1.1.0 -> semver@~7.0.0 Upstream issue open since Sep 2024, maintainer unresponsive - CVE-2025-66564 (sigstore/timestamp-authority): RISK ACCEPTED gh CLI has this compiled in, awaiting cli/cli PR #12299 to fix Memory exhaustion vuln requires attacker-controlled timestamp server Changes: - Dockerfile: Remove npm after pnpm install, remove copilot-cli - Added vulnerability-tracking.jsonl for CVE tracking with upstream issues - Added DOCKER_SCOUT_POLICY.md with manual policy configuration steps Upstream Issues Tracked: - npm/cli#8741 (glob) - CLOSED but unfixed - cli/cli#12299 (sigstore) - OPEN PR - alexbrazier/simple-update-notifier#30 (semver) - OPEN, no response 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: jason poley <jason.poley@gmail.com>
|
Will this PR or #12289 be merged soon? |
Contributor
Author
|
Looks like github.com/sigstore/sigstore-go is up-to-date now, so this is no longer needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps github.com/sigstore/sigstore-go from 1.1.3 to 1.1.4.
Release notes
Sourced from github.com/sigstore/sigstore-go's releases.
Commits
cc06490Bump github.com/sigstore/timestamp-authority/v2 (#552)45a9189Bump golangci/golangci-lint-action from 9.1.0 to 9.2.0 (#551)083ae4fBump actions/checkout from 6.0.0 to 6.0.1 (#550)2cdedeaBump the minor-patch group across 2 directories with 2 updates (#549)b5fe07aBump actions/setup-go from 6.0.0 to 6.1.0 (#548)60d26b7Bump actions/checkout from 5.0.0 to 6.0.0 (#547)41d11b5Bump golangci/golangci-lint-action from 9.0.0 to 9.1.0 (#546)bc9f48dBump the minor-patch group across 1 directory with 2 updates (#545)a187840Bump deps for sigstore libraries (#543)e639d1dBump sigstore-conformance to v0.0.24 (#542)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)