Repository navigation
deps: Bump bazel-registry -> d7b2089 (+envoy_toolshed) - #49411
Merged
Merged
Conversation
- `envoy_toolshed` -> 0.5.26.envoy Signed-off-by: dependency-envoy[bot] <148525496+dependency-envoy[bot]@users.noreply.github.com>
dependency-envoy
Bot
requested review from
RyanTheOptimist,
abeyad and
danzh2010
as code owners
November 18, 2026 20:17
phlax
approved these changes
Nov 18, 2026
Member
|
/retest flakey android |
phlax
enabled auto-merge (squash)
November 18, 2026 20:24
phlax
added a commit
that referenced
this pull request
Nov 18, 2026
The dependency bot (`ci/dependency/update.sh`) bumps a `bazel_dep` and leaves the `release_date` of the dependency in `deps.yaml` as it was. The hook that updated it for the WORKSPACE updater went with WORKSPACE (#47217), so every bump since has had a stale date (#49388 needed six fixed by hand), and now that the release dates check is back (#48705) the `deps` precheck of a bump fails on it. This adds `//tools/dependency:release_dates` (`release_date_updater`, envoyproxy/toolshed#5626 and envoyproxy/toolshed#5630), which fixes the dates in `bazel/deps.yaml` and `api/bazel/deps.yaml` with the ones that the checker (`//tools/dependency:check`) looks up: ```console $ bazel run //tools/dependency:release_dates -- gperftools Checking the release dates of: gperftools bazel/deps.yaml: gperftools 2026-03-06 -> 2026-10-21 ``` `deps.update` (the bot's `bazel` task) and `registry` with named modules (its `registry` task) now run it for the modules they update. Only those are looked up, as each is a request to GitHub, a module can be named as the module (`msgpack-c`) where its metadata key differs (`msgpack-cxx`), and a module with no metadata is skipped. It needs the `GITHUB_TOKEN` that the workflow already gives the update. Not covered: `registry` with `all`, where the updated modules are not known at that point; their dates are left to the `deps` check. A dependency with metadata in both files (`envoy_toolshed`) is fixed in both: the check reads the API file's date. Risk Level: Low (dependency tooling only) Testing: The `bazel` task was run from a branch with these changes against a pre-release of the toolshed module ([run 44363626118](https://github.com/envoyproxy/envoy/actions/runs/44363626118), `gperftools msgpack-c`, no PR): the diff it produced has the `gperftools` date fixed alongside the `MODULE.bazel` and lockfile changes. There the step was in `do_ci.sh`; it is now in `deps_update`. The `registry` path, and the fix of a dependency in both files (toolshed 0.5.26.envoy, #49411), have not been run. Docs Changes: `ci/README.md` Release Notes: N/A Signed-off-by: Ryan Northey <ryan@synca.io>
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.
Created by Envoy dependency bot for @phlax
envoy_toolshed-> 0.5.26.envoyenvoy_toolshed-> 0.5.26.envoySigned-off-by: dependency-envoy[bot] <148525496+dependency-envoy[bot]@users.noreply.github.com>