Skip to content

deps(actions)(deps): bump sigstore/cosign-installer from 3.9.1 to 4.1.2#7

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

deps(actions)(deps): bump sigstore/cosign-installer from 3.9.1 to 4.1.2#7
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/sigstore/cosign-installer-4.1.2

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github May 22, 2026

Bumps sigstore/cosign-installer from 3.9.1 to 4.1.2.

Release notes

Sourced from sigstore/cosign-installer's releases.

v4.1.2

What's Changed

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

... (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.9.1 to 4.1.2.
- [Release notes](https://github.com/sigstore/cosign-installer/releases)
- [Commits](sigstore/cosign-installer@398d4b0...6f9f177)

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

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

dependabot Bot commented on behalf of github May 22, 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.

RelativisticJet added a commit that referenced this pull request May 23, 2026
The "Run module-level tests" step in ci.yml referenced
tests/test_wl_hmac_key.py — a file that never existed. The result
was every Unit Tests run on main red since the workflow landed
(verified via gh run list --workflow=ci.yml -- 5+ consecutive
failures on commits a48f6c2 / 4330149 / ab53066 / 91d9d22 /
b14b3c9 all citing "ERROR: file or directory not found:
tests/test_wl_hmac_key.py", exit code 4).

HMAC coverage is already provided by tests/unit/test_hmac_key.py
+ tests/unit/test_hmac_sig_fuzz.py, both of which run via the
prior `pytest tests/unit/` step. So removing the broken line
loses zero coverage — it just unblocks the workflow.

Same shape of fix as the round-7-B4 cleanup that removed a
stale tests/test_wl_filelock.py reference. Updated the
preamble comment to document BOTH missing-file gotchas so
they don't get re-added by a future contributor reading the
old comment as a TODO.

Side benefit: this also unblocks the Unit Tests check on every
open Dependabot PR (#7-#16), which were all red on the same
missing-file error.
@RelativisticJet
Copy link
Copy Markdown
Owner

Closing per locked decision in docs/DECISION_LOG.md (2026-05-20 row 1):

Leave sigstore/cosign-installer@v3 deliberately unbumped despite v4.1.2 being GA. [...] bumping cosign-installer@v3 → v4 MUST be done in a commit that also re-runs docs/RELEASE_CHECKLIST.md §8 on a fresh v0.0.0-sigstore-test-N+1 tag. The §8 verification is keyed to the signing-installer version; changing it invalidates the static verification artifact.

The 2026-05-13 / 2026-05-20 Sigstore §8 dry-runs are our authoritative supply-chain verification artifact. Bumping cosign-installer without re-running §8 would invalidate them. This is a dedicated cycle scheduled separately; please don't re-propose without the §8 re-run plan.

If a security advisory against cosign-installer v3 forces our hand, see the same DECISION_LOG row for the cosign-release v2.x ↔ v3+ --bundle compatibility note.

@dependabot @github
Copy link
Copy Markdown
Author

dependabot Bot commented on behalf of github May 23, 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.

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.

1 participant