Skip to content

chore(deps): pin dependencies#673

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/github-actions
Open

chore(deps): pin dependencies#673
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/github-actions

Conversation

@renovate

@renovate renovate Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Pending
actions/add-to-project action pinDigest 5afcf98
actions/cache action major v5v6
actions/checkout action major v6v7 v7.0.1
actions/setup-java action pinDigest 03ad4de
actions/setup-node action major v6v7
actions/upload-artifact action pinDigest 043fb46
docker/login-action action minor v4.2.0v4.4.0 v4.5.1 (+1)
docker/metadata-action (changelog) action digest 030e881dc80280
docker/setup-buildx-action (changelog) action digest 4d04d5dbb05f3f
node uses-with minor 2424.18.0
sigstore/cosign uses-with major v2.2.4v3.1.2

Release Notes

actions/cache (actions/cache)

v6.1.0

Compare Source

What's Changed

Full Changelog: actions/cache@v6...v6.1.0

v6.0.0

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v6.0.0

v6

Compare Source

v5.1.0

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v5.1.0

v5.0.5

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v5.0.5

v5.0.4

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v5...v5.0.4

v5.0.3

Compare Source

What's Changed

Full Changelog: actions/cache@v5...v5.0.3

v5.0.2: v.5.0.2

Compare Source

v5.0.2
What's Changed

When creating cache entries, 429s returned from the cache service will not be retried.

v5.0.1

Compare Source

[!IMPORTANT]
actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.


v5.0.1
What's Changed
v5.0.0
What's Changed

Full Changelog: actions/cache@v5...v5.0.1

actions/checkout (actions/checkout)

v7.0.0

Compare Source

v7

Compare Source

v6.1.0

Compare Source

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

actions/setup-node (actions/setup-node)

v7.0.0

Compare Source

What's Changed
Enhancements:
Bug fixes:
Documentation updates:
Dependency update:
New Contributors

Full Changelog: actions/setup-node@v6...v7.0.0

v7

Compare Source

v6.5.0

Compare Source

What's Changed

Full Changelog: actions/setup-node@v6.4.0...v6.5.0

v6.4.0

Compare Source

What's Changed

Dependency updates:

New Contributors

Full Changelog: actions/setup-node@v6...v6.4.0

v6.3.0

Compare Source

What's Changed

Enhancements:

When using node-version-file: package.json, setup-node now prefers devEngines.runtime over engines.node.

Dependency updates:
Bug fixes:

New Contributors

Full Changelog: actions/setup-node@v6...v6.3.0

v6.2.0

Compare Source

What's Changed

Documentation
Dependency updates:

New Contributors

Full Changelog: actions/setup-node@v6...v6.2.0

v6.1.0

Compare Source

What's Changed

Enhancement:
Dependency updates:
Documentation update:

Full Changelog: actions/setup-node@v6...v6.1.0

docker/login-action (docker/login-action)

v4.4.0

Compare Source

v4.3.0

Compare Source

Full Changelog: docker/login-action@v4.2.0...v4.3.0

actions/node-versions (node)

v24.18.0: 24.18.0

Compare Source

Node.js 24.18.0

v24.17.0: 24.17.0

Compare Source

Node.js 24.17.0

v24.16.0: 24.16.0

Compare Source

Node.js 24.16.0

v24.15.0: 24.15.0

Compare Source

Node.js 24.15.0

v24.14.1: 24.14.1

Compare Source

Node.js 24.14.1

v24.14.0: 24.14.0

Compare Source

Node.js 24.14.0

v24.13.1: 24.13.1

Compare Source

Node.js 24.13.1

v24.13.0: 24.13.0

Compare Source

Node.js 24.13.0

v24.12.0: 24.12.0

Compare Source

Node.js 24.12.0

v24.11.1: 24.11.1

Compare Source

Node.js 24.11.1

v24.11.0: 24.11.0

Compare Source

Node.js 24.11.0

v24.10.0: 24.10.0

Compare Source

Node.js 24.10.0

v24.9.0: 24.9.0

Compare Source

Node.js 24.9.0

v24.8.0: 24.8.0

Compare Source

Node.js 24.8.0

v24.7.0: 24.7.0

Compare Source

Node.js 24.7.0

v24.6.0: 24.6.0

Compare Source

Node.js 24.6.0

v24.5.0: 24.5.0

Compare Source

Node.js 24.5.0

v24.4.1: 24.4.1

Compare Source

Node.js 24.4.1

v24.4.0: 24.4.0

Compare Source

Node.js 24.4.0

v24.3.0: 24.3.0

Compare Source

Node.js 24.3.0

v24.2.0: 24.2.0

Compare Source

Node.js 24.2.0

v24.1.0: 24.1.0

Compare Source

Node.js 24.1.0

v24.0.2: 24.0.2

Compare Source

Node.js 24.0.2

v24.0.1: 24.0.1

Compare Source

Node.js 24.0.1

sigstore/cosign (sigstore/cosign)

v3.1.2

Compare Source

This may be the last Cosign v3.1 release, as we finish deprecations and removing unused functionality. Soon we'll start work on Cosign v4 where we will remove things that are currently deprecated. We'll continue to support Cosign v3, with it's opt-in backwards compatibility, as described in our versioning policy.

If you haven't already, now is an excellent time to move to the bundle format that has been supported since Cosign v2.6.

We have received a ton of fixes over the past month from folks using Cosign in a variety of environments - thank you all!

Deprecations

Features

Fixes

  • eb3bb86 Guard against empty certificate PEM in mutate.Signature (#​4998)
  • 089731c fix(download): Validate predicate type for new bundle format
  • d996ce1 Skip nil subject entries in IntotoSubjectClaimVerifier (#​5016)
  • 8ca5b20 Fix Makefile: fall back to "unknown" version info when built outside a git repo (#​5000)
  • df78bf6 fix(verify): skip identity validation for security keys (#​5012)
  • aebdc3a fix: include artifactType in OCI 1.1 signature referrer manifest
  • c0edaac Allow attestation download to handle both bundle types (#​4996)
  • a8642c7 Fix panic in dockerfile verify on malformed FROM lines (#​4979)
  • ef3e3b4 fix(release): restore signing-step auth and fail on image signing errors (#​4978)
  • 16ddbcf feat(signing-config): add --base-config flag to override services from base config (#​4977)
  • f17f812 fix: pass NewBundleFormat to KeyOpts in sign command (#​4981)
  • 6ef8d9d fix: ignore build stage references in dockerfile verify (#​4961)
  • 8dbdef5 fix: allow '=' in annotation values (#​4957)

Cleanup

Documentation

  • 8184126 feat: improve verify flag shell completions (#​4965)
  • ed0efe8 docs: fix Short style and add Example fields to piv-tool subcommands (#​4942)
  • d41b86c docs: add Example fields to env and bundle create commands (#​4941)
  • 8a7174a docs: fix Short style and add Example fields to pkcs11-tool subcommands
Thanks to all contributors!

v3.1.1

Compare Source

What's Changed

Note: v3.1.0 was skipped due to a bug in our release pipeline. v3.1.1 is identical to v3.1.0

This release deprecates a number of flags related to verification material input for trust root material, as well as the bundle format, standardized across Sigstore SDKs, which is now the default output and input for signing and verifying respectively. You may continue to use the deprecated flags with Cosign v3.x releases. The deprecated flags will be removed in a future Cosign v4 release.

This release also updates the signing path for logging to Rekor v2. DSSE attestations will be logged as hashed entries, using the DSSE's pre-auth encoding (PAE). This should unblock developers who want to upload large signed DSSEs such as SBOMs.

  • Initialize PKCS11 slots Before Getting Token Info in #​4803
  • Sign exclusively via sigstore-go in #​4618
  • bundle create: Prevent IgnoreTlog when bundle contains SET in #​4829
  • Require bundle output or registry upload in #​4785
  • fix(load): pass NameOptions to name.ParseReference in #​4786
  • fix: honor --digestAlg when hashing a blob in verify-blob-attestation in #​4813
  • Deprecate Flags for v4: Certificates in #​4822
  • Deprecate flags signing config in #​4844
  • Deprecate flags bundle in #​4838
  • Fix typo in map of verify command fields unsupported for new bundle format in #​4853
  • Add bundle upgrade command in #​4820
  • Deprecate Flags for v4 in #​4854
  • fix: close file descriptor leaked in WriteSignedImageIndexImages loop in #​4869
  • fix: use Header.Set to prevent duplicate Authorization on retry in #​4870
  • feat(cli): add Rekor v2 flag to cosign signing-config create in #​4868
  • Fix crash verifying timestamps when no timestamp was verified in #​4881
  • Deprecate Flags for v4: OCI Referrers in #​4804
  • Use the configured Target Repository more consistently in #​4836
  • fix: check HTTP status code in LoadFileOrURL in #​4877
  • Fix unsafe type assertion in Rego policy evaluation by in #​4882
  • Fix Ed25519ph check to respect custom signing configs in sign-blob in #​4880
  • Enable initialize command output in conformance in #​4892
  • verify: return TUF errors for new bundle trusted roots in #​4878
  • Deprecate subcommands in #​4894
  • Remove docstring references to deprecated flags in #​4910
  • fix(verify): Attach detached certificates to static signatures via wrapped verifier in #​4737
  • fix(verify): copy CheckOpts inside VerifyNewBundle to fix data race in #​4917
  • Update sigstore-go to v1.2.0 in #​4914

Full Changelog: sigstore/cosign@v3.0.6...v3.1.1

v3.0.6

Compare Source

Changelog

v3.0.6 resolves GHSA-w6c6-c85g-mmv6. This release also adds support for signing with OpenBao-managed keys.

Thanks to all contributors!

v3.0.5

Compare Source

Deprecations

Features

  • Automatically require signed timestamp with Rekor v2 entries (#​4666)
  • Allow --local-image with --new-bundle-format for v2 and v3 signatures (#​4626)
  • Add mTLS support for TSA client connections when signing with a signing config (#​4620)
  • Enforce TSA requirement for Rekor v2, Fuclio signing (#​4683)

Bug Fixes

  • Add empty predicate to cosign sign when payload type is application/vnd.in-toto+json (#​4635)
  • fix: avoid panic on malformed attestation payload (#​4651)
  • fix: avoid panic on malformed tlog entries (#​4649)
  • fix: avoid panic on malformed replace payload (#​4653)
  • Gracefully fail if bundle payload body is not a string (#​4648)
  • Verify validity of chain rather than just certificate (#​4663)
  • fix: avoid panic on malformed tlog entry body (#​4652)

Documentation

  • docs(cosign): clarify RFC3161 revocation semantics (#​4642)
  • Fix typo in CLI help (#​4701)

v3.0.4

Compare Source

v3.0.4 resolves GHSA-whqx-f9j3-ch6m.

Changes

  • Fix bundle verify path for old bundle/trusted root (GHSA-whqx-f9j3-ch6m) (#​4623)
  • Optimize cosign tree performance by caching digest resolution (#​4612)
  • Don't require a trusted root to verify offline with a key (#​4613)
  • Support default services for trusted-root and signing-config creation (#​4592)

v3.0.3

Compare Source

Thank you for all of your feedback on Cosign v3! v3.0.3 fixes a number of bugs reported by
the community along with adding compatibility for the new bundle format and attestation
storage in OCI to additional commands. We're continuing to work on compatibility with
the remaining commands and will have a new release shortly. If you run into any problems,
please file an issue

Changes

  • 4554: Closes 4554 - Add warning when --output* is used (#​4556)
  • Protobuf bundle support for subcommand clean (#​4539)
  • Add staging flag to initialize with staging TUF metadata
  • Updating sign-blob to also support signing with a certificate (#​4547)
  • Protobuf bundle support for subcommands save and load (#​4538)
  • Fix cert attachment for new bundle with signing config
  • Fix OCI verification with local cert - old bundle
  • Deprecate tlog-upload flag (#​4458)
  • fix: Use signal context for sign cli package.
  • update offline verification directions (#​4526)
  • Fix signing/verifying annotations for new bundle
  • Add support to download and attach for protobuf bundles (#​4477)
  • Add --signing-algorithm flag (#​3497)
  • Refactor signcommon bundle helpers
  • Add --bundle and fix --upload for new bundle
  • Pass insecure registry flags through to referrers
  • Add protobuf bundle support for tree subcommand (#​4491)
  • Remove stale embed import (#​4492)
  • Support multiple container identities
  • Fix segfault when no attestations are found (#​4472)
  • Use overridden repository for new bundle format (#​4473)
  • Remove --out flag from cosign initialize (#​4462)
  • Deprecate offline flag (#​4457)
  • Deduplicate code in sign/attest* and verify* commands (#​4449)
  • Cache signing config when calling initialize (#​4456)

v3.0.2

Compare Source

v3.0.2 is a functionally equivalent release to v3.0.0 and v3.0.1, with a fix for CI to publish signed releases in the new bundle format.

  • Note that the --bundle flag specifying an output file to write the Sigstore bundle (which contains all relevant verification material) has moved from optional to required in v3.

Changes

  • choose different signature filename for KMS-signed release signatures (#​4448)
  • Update rekor-tiles version path (#​4450)

v3.0.1

Compare Source

v3.0.1 is an equivalent release to v3.0.0, which was never published due to a failure in our CI workflows.

  • Note that the --bundle flag specifying an output file to write the Sigstore bundle (which contains all relevant verification material) has moved from optional to required in v3.

Changes

  • update goreleaser config for v3.0.0 release (#​4446)

v2.6.4

Compare Source

This release is a backport of OCI manifest fixes, and better support for cosign attestation download when you are using a mix of old Cosign signatures with the more recent bundle format.

We strongly encourage folks to continue their migration to the bundle format. The Cosign v3.1.x releases support both formats; the primary change being that the default for signing is the bundle format (although you can specify --new-bundle-format=false to sign with the old format). The verification commands in Cosign v3.1.x support both formats, and will try to detect the format for you for maximum compatibility.

Changelog

  • 26261f0 Allow attestation download to handle both bundle types (#​4996) (#​5017)
  • d49a0c1 fix: include artifactType in OCI 1.1 signature referrer manifest (cherry-pick PR-4997 to release-2.6) (#​5002)
Thanks to all contributors!

v2.6.3

Compare Source

Changelog

v2.6.3 resolves GHSA-w6c6-c85g-mmv6.

Thanks to all contributors!

v2.6.2

Compare Source

v2.6.2 resolves GHSA-whqx-f9j3-ch6m.

Changes

v2.6.1

Compare Source

Bug Fixes

  • Partially populate the output of cosign verify when working with new bundles (#​4416)
  • Bump sigstore-go, move conformance back to tagged release (#​4426)

v2.6.0

Compare Source

v2.6.0 introduces a number of new features, including:

  • Signing an in-toto statement rather than Cosign constructing one from a predicate, along with verifying a statement's subject using a digest and digest algorithm rather than providing a file reference (#​4306)
  • Uploading a signature and its verification material (a "bundle") as an OCI Image 1.1 referring artifact, completing #​3927 (#​4316)
  • Providing service URLs for signing and attesting using a SigningConfig. Note that this is required when using a Rekor v2 instance (#​4319)

Example generation and verification of a signed in-toto statement:

cosign attest-blob --new-bundle-format=true --bundle="digest-key-test.sigstore.json" --key="cosign.key" --statement="../sigstore-go/examples/sigstore-go-signing/intoto.txt"
cosign verify-blob-attestation --bundle="diges

> ✂ **Note**
> 
> PR body was truncated to here.


</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - "before 6am on monday"
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://redirect.github.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/frankframework/insights).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yODAuMCIsInVwZGF0ZWRJblZlciI6IjQzLjI4MC4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbIkNJL0NEIiwiRGVwZW5kZW5jaWVzIiwiYXV0b21lcmdlIl19-->

@renovate renovate Bot added automerge dependencies Pull requests that update a dependency file CI/CD labels Jul 27, 2026
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge CI/CD dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants