Repository navigation
Bump bazel-contrib/setup-bazel from 0.19.0 to 0.19.1 - #1013
Merged
helly25 merged 13 commits intoOct 23, 2026
Merged
Conversation
Bumps [bazel-contrib/setup-bazel](https://github.com/bazel-contrib/setup-bazel) from 0.19.0 to 0.19.1. - [Release notes](https://github.com/bazel-contrib/setup-bazel/releases) - [Commits](bazel-contrib/setup-bazel@0.19.0...0.19.1) --- updated-dependencies: - dependency-name: bazel-contrib/setup-bazel dependency-version: 0.19.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…13-setup-bazel-ci
…13-setup-bazel-ci
…13-setup-bazel-ci
helly25
deleted the
dependabot/github_actions/bazel-contrib/setup-bazel-0.19.1
branch
October 23, 2026 03:10
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
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 bazel-contrib/setup-bazel from 0.19.0 to 0.19.1.
AG;DR
Update setup-bazel from 0.19.0 to 0.19.1 in the main, release, fuzz, benchmarks and benchmark-backfill workflows. Update
tools/release_prep_test.shto require the same new pin for every workflow reference, preserving the version-policy guard.Current head:
10894f4f712aab0290317fe6a2de3e2cfb696985, synchronized with main801087f3e9a8bf192928896c7f24c369003d1e7bafter PR 1011 merged. The LLVM selector and Ubuntu runtime compatibility fixes are now on main; this PR's remaining diff is the five action-version updates plus their policy-test expectations. The synchronization satisfies the repository's strict base-freshness requirement.Validation:
bash tools/release_prep_test.sh, focused pre-commit checks for all six changed files, andgit diff --checkpass on the synchronized head.git diff 57313d9d6ccbf0b6f10144f906ab42bb3c42cc7c HEADis empty: the synchronization preserves the exact file tree that passed the complete preceding CI run, including all 294 translation units in the full clang-tidy scan.Post-merge verification of main
3dbc47cc2a1d84c0e6b60f0a497c1d3ce160351f:ae62c828a3, whose LLVM 23.1.2 LLD requires ICU 70 absent from Ubuntu 26.04. The current comparison uses corrected parent801087f3e9a8bf192928896c7f24c369003d1e7b, preserving each revision’s actual toolchain configuration.Upstream release information generated by Dependabot follows.
Release notes
Sourced from bazel-contrib/setup-bazel's releases.
Commits
104e3eeRelease 0.19.10114cb1chore(deps): update dependency yaml to v2.9.1 (#177)c077f7fchore(deps): update dependency@actions/cacheto v6.3.0 (#178)2c206a1chore(deps): update node.js to v24.21.0 (#176)e98ce48fix(deps): update dependency@vercel/nccto ^0.45.0 (#175)c1cfa6fchore(deps): update node.js to v24.20.0 (#174)5bab119chore(deps): update node.js to v24.18.1 (#173)ef83a47chore(deps): update dependency@actions/cacheto v6.2.0 (#169)5ff9befchore(deps): update actions/checkout action to v7 (#170)46d9ed7chore(deps): update node.js to v24.18.0 (#168)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 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)