Skip to content

build(deps): bump sigstore/cosign-installer from 3.7.0 to 4.1.1#167

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/sigstore/cosign-installer-4.1.1
Closed

build(deps): bump sigstore/cosign-installer from 3.7.0 to 4.1.1#167
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/sigstore/cosign-installer-4.1.1

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Apr 21, 2026

Bumps sigstore/cosign-installer from 3.7.0 to 4.1.1.

Release notes

Sourced from sigstore/cosign-installer's releases.

v4.1.1

What's Changed

Full Changelog: sigstore/cosign-installer@v4.1.0...v4.1.1

v4.1.0

What's Changed

We recommend updating as soon as possible as this includes bug fixes for Cosign. We also recommend removing with: cosign-release and strongly discourage using cosign-release unless you have a specific reason to use an older version of Cosign.

Full Changelog: sigstore/cosign-installer@v4.0.0...v4.1.0

v4.0.0

What's Changed?

Note: You must upgrade to cosign-installer v4 if you want to install Cosign v3+. You may still install Cosign v2.x with cosign-installer v4.

In version v3+, using cosign sign-blob requires adding the --bundle flag which may require you to update your signing command.

  • Add support for Cosign v3 releases (#201)

v3.10.1

What's Changed?

Note: cosign-installer v3.x cannot be used to install Cosign v3.x. You must upgrade to cosign-installer v4 in order to use Cosign v3.

Note: This is planned to be the final release of Cosign v2, though we will cut new releases for any critical security or bug fixes. We recommend transitioning to Cosign v3.

  • Bump default Cosign to v2.6.1 (#203)

v3.10.0

What's Changed

Full Changelog: sigstore/cosign-installer@v3.9.2...v3.10.0

v3.9.2

What's Changed

Full Changelog: sigstore/cosign-installer@v3.9.1...v3.9.2

v3.9.1

... (truncated)

Commits

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [sigstore/cosign-installer](https://github.com/sigstore/cosign-installer) from 3.7.0 to 4.1.1.
- [Release notes](https://github.com/sigstore/cosign-installer/releases)
- [Commits](sigstore/cosign-installer@dc72c7d...cad07c2)

---
updated-dependencies:
- dependency-name: sigstore/cosign-installer
  dependency-version: 4.1.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Apr 21, 2026

Labels

The following labels could not be found: ci, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot requested a review from systemslibrarian as a code owner April 21, 2026 00:42
@codecov-commenter
Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Copy link
Copy Markdown
Owner

Holding this bump pending a deliberate Cosign v2-vs-v3 decision.

cosign-installer@v4 defaults to installing Cosign v3.0.5, and Cosign v3 has a breaking change to cosign sign-blob: it now requires a --bundle flag. Our release.yml:102 call is:

cosign sign-blob --yes "$file" --output-signature "${file}.sig" --output-certificate "${file}.pem"

Merging as-is would break release artifact signing.

Two ways forward — pick one and I'll wire it up:

  1. Stay on Cosign v2. Bump to cosign-installer@v4 and pin cosign-release: v2.6.1 in the workflow step. Smallest diff; preserves current sig-blob output format.
  2. Upgrade to Cosign v3. Bump to cosign-installer@v4 (default v3 install) and add --bundle release.bundle.json to the sign-blob call. Drops --output-signature/--output-certificate which become bundle fields. Verifiers will need updating to consume .bundle.json.

Auto-resolve this PR is unsafe either way; needs operator input.

systemslibrarian added a commit that referenced this pull request May 4, 2026
Resolves dependabot PR #167.

`cosign-installer@v4` defaults to installing Cosign v3, which has a
breaking change to `cosign sign-blob`: the new flag `--bundle` is
required and the legacy `--output-signature` / `--output-certificate`
flags produce no output. Our `release.yml::Sign artifacts with
Sigstore` step still uses the legacy flag set, and downstream
verifiers consume `.sig` + `.pem` separately.

To get the installer upgrade without the runtime breaking change:
add `with: cosign-release: 'v2.6.1'`. The v4 installer line
explicitly supports installing Cosign v2.x — quoting the upstream
release notes:

> You may still install Cosign v2.x with cosign-installer v4.

When the project is ready to migrate to Cosign v3 (which adds
SLSA-level provenance bundles + Sigstore v2 transparency log
support), the migration is:

1. Remove the `cosign-release: 'v2.6.1'` pin.
2. Update `cosign sign-blob ... --output-signature S --output-certificate C`
   to `cosign sign-blob ... --bundle release.bundle.json`.
3. Update verifiers to consume `.bundle.json` instead of `.sig`/`.pem`.

That is a separately planned migration; this commit just clears the
dependabot PR with zero change to release-artifact format.

Closes #167.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Owner

Superseded by commit 8ba892d on audit/cat-mode-fixes (PR #172). That commit takes the same installer SHA bump (v4.1.1) but additionally pins cosign-release: 'v2.6.1' so the runtime Cosign binary stays on v2 — preserving the current sign-blob --output-signature/--output-certificate output format and avoiding a downstream verifier break. The Cosign v3 migration (drop pin, add --bundle, update verifiers) is recorded in the commit message as a separately planned change.

Closing as superseded.

@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github May 4, 2026

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot Bot deleted the dependabot/github_actions/sigstore/cosign-installer-4.1.1 branch May 4, 2026 12:31
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