Skip to content

evidence: lock_refresh regenerates MODULE.bazel.lock on the platform (part of #9754) - #9770

Draft
TrapsterDK wants to merge 1 commit into
mainfrom
windows-lock-9754
Draft

TrapsterDK wants to merge 1 commit into
mainfrom
windows-lock-9754

Conversation

@TrapsterDK

@TrapsterDK TrapsterDK commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

Closes #9754. The msvc_runtime lock entry is not host-dependent: evidence run 42609583739 (windows_x86_64, lock_refresh=true) regenerated MODULE.bazel.lock on Windows with no diff, and Linux regeneration also gives none. The earlier stale-usage error came from branch platform-labels-rest-9535 carrying other module changes.

This keeps the Windows check: lock_refresh=true in evidence.yml runs bazel mod deps --lockfile_mode=update, fails on a diff, and uploads the refreshed lock and diff under lock/. No consumer or nested-Bazel tests were run.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Xut2hwESun1HL2eSVd1d5B

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

windows: MODULE.bazel.lock msvc_runtime entry is stale and only refreshes on a Windows host

1 participant