chore(locks): regenerate for yanked build==1.5.1 (#353)#367
Merged
haiyuan-eng-google merged 1 commit intoJul 15, 2026
Merged
Conversation
…oogleCloudPlatform#353) Upstream yanked build==1.5.1, so the deterministic two-phase regeneration (regen-locks.sh, converged in one phase inside the pinned base image) now resolves build==1.5.0 in pip-tools.lock and build-requirements.lock. This is the drift currently failing the Hash-lock drift check on main and on PR GoogleCloudPlatform#366.
This was referenced Jul 15, 2026
haiyuan-eng-google
approved these changes
Jul 15, 2026
haiyuan-eng-google
merged commit Jul 15, 2026
96a079f
into
GoogleCloudPlatform:main
23 checks passed
Open
26 tasks
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
2 participants
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.
Focused lock refresh per the #353 operational review: upstream yanked
build==1.5.1(PyPI), soregen-locks.sh(run inside the pinned base image; generator converged in one phase) now resolvesbuild==1.5.0indeploy/otlp_receiver/pip-tools.lockandproducers/build-requirements.lock— the exact drift failing the Hash-lock drift check onmain(d7b41e3) and blocking docs PR #366 and guard PR #369.Only the two
build==pins and their hashes change; the new hashes match PyPI's non-yanked 1.5.0 wheel and sdist.After this merges, update/rebase #366 and #369 onto the new
mainso their pull-request workflow runs contain this fix — a plain re-run of their existing runs reuses the originalGITHUB_SHAand cannot pick it up (docs).Part of #353.