Skip to content

Bump the actions group with 2 updates - #4472

Merged
kubernetes-prow[bot] merged 1 commit into
masterfrom
dependabot/github_actions/actions-d862b53b3f
Jul 20, 2026
Merged

Bump the actions group with 2 updates#4472
kubernetes-prow[bot] merged 1 commit into
masterfrom
dependabot/github_actions/actions-d862b53b3f

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 20, 2026

Copy link
Copy Markdown
Contributor

Bumps the actions group with 2 updates: kubernetes-sigs/release-actions/setup-bom and kubernetes-sigs/release-actions/setup-tejolote.

Updates kubernetes-sigs/release-actions/setup-bom from 0.4.3 to 0.4.4

Release notes

Sourced from kubernetes-sigs/release-actions/setup-bom's releases.

v0.4.4

📢 What's New

This release bumps all the tools versions and also marks the point where we switch signing and verification from the old detached signatures to sigstore bundles. And as of now, instead of verifying with cosing, we now use a single AMPEL policy to verify both old signatures and the new bundles.

What's Changed

New Contributors

Full Changelog: kubernetes-sigs/release-actions@v0.4.3...v0.4.4

Commits
  • c130b44 Merge pull request #171 from binerbot/update-setup-release-notes-v0.21.1
  • 6b5a664 Merge pull request #172 from binerbot/update-publish-release-v0.21.1
  • a2be64d Merge pull request #170 from binerbot/update-setup-zeitgeist-v0.7.0
  • f3ceaf2 Merge pull request #169 from binerbot/update-setup-tejolote-v0.5.0
  • 7818666 Update setup-release-notes default version to v0.21.1
  • 32de787 Update publish-release default version to v0.21.1
  • 0bf9637 Update setup-zeitgeist default version to v0.7.0
  • d35e105 Update setup-tejolote default version to v0.5.0
  • 9eae6f1 Merge pull request #168 from puerco/verify-with-policy
  • 85c18ac Verify binaries with policy instead of cosign
  • Additional commits viewable in compare view

Updates kubernetes-sigs/release-actions/setup-tejolote from 0.4.3 to 0.4.4

Release notes

Sourced from kubernetes-sigs/release-actions/setup-tejolote's releases.

v0.4.4

📢 What's New

This release bumps all the tools versions and also marks the point where we switch signing and verification from the old detached signatures to sigstore bundles. And as of now, instead of verifying with cosing, we now use a single AMPEL policy to verify both old signatures and the new bundles.

What's Changed

New Contributors

Full Changelog: kubernetes-sigs/release-actions@v0.4.3...v0.4.4

Commits
  • c130b44 Merge pull request #171 from binerbot/update-setup-release-notes-v0.21.1
  • 6b5a664 Merge pull request #172 from binerbot/update-publish-release-v0.21.1
  • a2be64d Merge pull request #170 from binerbot/update-setup-zeitgeist-v0.7.0
  • f3ceaf2 Merge pull request #169 from binerbot/update-setup-tejolote-v0.5.0
  • 7818666 Update setup-release-notes default version to v0.21.1
  • 32de787 Update publish-release default version to v0.21.1
  • 0bf9637 Update setup-zeitgeist default version to v0.7.0
  • d35e105 Update setup-tejolote default version to v0.5.0
  • 9eae6f1 Merge pull request #168 from puerco/verify-with-policy
  • 85c18ac Verify binaries with policy instead of cosign
  • Additional commits viewable in compare view

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 <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

@dependabot
Bump the actions group with 2 updates
bd6a22c 
Bumps the actions group with 2 updates: [kubernetes-sigs/release-actions/setup-bom](https://github.com/kubernetes-sigs/release-actions) and [kubernetes-sigs/release-actions/setup-tejolote](https://github.com/kubernetes-sigs/release-actions).


Updates `kubernetes-sigs/release-actions/setup-bom` from 0.4.3 to 0.4.4
- [Release notes](https://github.com/kubernetes-sigs/release-actions/releases)
- [Changelog](https://github.com/kubernetes-sigs/release-actions/blob/main/RELEASE.md)
- [Commits](kubernetes-sigs/release-actions@8753ea6...c130b44)

Updates `kubernetes-sigs/release-actions/setup-tejolote` from 0.4.3 to 0.4.4
- [Release notes](https://github.com/kubernetes-sigs/release-actions/releases)
- [Changelog](https://github.com/kubernetes-sigs/release-actions/blob/main/RELEASE.md)
- [Commits](kubernetes-sigs/release-actions@8753ea6...c130b44)

---
updated-dependencies:
- dependency-name: kubernetes-sigs/release-actions/setup-bom
  dependency-version: 0.4.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
- dependency-name: kubernetes-sigs/release-actions/setup-tejolote
  dependency-version: 0.4.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added area/dependency Issues or PRs related to dependency changes ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. labels Jul 20, 2026
@kubernetes-prow

kubernetes-prow Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kubernetes-prow kubernetes-prow Bot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Jul 20, 2026
@kubernetes-prow
kubernetes-prow Bot requested review from jimangel and jrsapi July 20, 2026 01:53
@kubernetes-prow kubernetes-prow Bot added area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. needs-priority size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 20, 2026
cpanato
cpanato approved these changes Jul 20, 2026
View reviewed changes

@cpanato cpanato left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/retest

@kubernetes-prow kubernetes-prow Bot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 20, 2026
@kubernetes-prow

kubernetes-prow Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, dependabot[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubernetes-prow kubernetes-prow Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 20, 2026
@kubernetes-prow
kubernetes-prow Bot merged commit 587dab1 into master Jul 20, 2026
11 checks passed
@kubernetes-prow
kubernetes-prow Bot deleted the dependabot/github_actions/actions-d862b53b3f branch July 20, 2026 02:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cpanato cpanato cpanato approved these changes
@jimangel jimangel Awaiting requested review from jimangel
@jrsapi jrsapi Awaiting requested review from jrsapi

Assignees

@cpanato cpanato

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/dependency Issues or PRs related to dependency changes area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. sig/release Categorizes an issue or PR as relevant to SIG Release. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@cpanato