fix(ci): use own md5 tool for Bazel 9 compatibility#1007
Merged
cgrindel merged 1 commit intobazelbuild:mainfrom Jan 24, 2026
Merged
Conversation
7c64b68 to
2f278a8
Compare
This was referenced Jan 21, 2026
meteorcloudy
added a commit
that referenced
this pull request
Jan 22, 2026
Updates `ossf/scorecard-action` from `v2` to `v2.4.0` and `actions/upload-artifact` from `v3` to `v4` to comply with GitHub's deprecation notice (https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions). As of January 22, 2025, workflows using v3 artifact actions fail with: ``` ##[error]This request has been automatically failed because it uses a deprecated version of `actions/upload-artifact: v3`. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/. ``` Fixes #1012. Note: CI still fails due to #1010, for which there's a proposed countermeasure: #1007.
2f278a8 to
4fdfce4
Compare
md5 tool for Bazel 9 compatmd5 tool for Bazel 9 compatibility
cefebab to
93cfdf1
Compare
Bazel 9.0.0 flipped `--incompatible_strict_action_env` to `true` by default, restricting `PATH` to `/bin:/usr/bin:/usr/local/bin`. On macOS, this broke a few tests relying on the `md5sum` command: ``` Executing genrule //tests/deb:generate_md5sums failed: (Exit 127): [...] [...] /bin/bash: md5sum: command not found ``` This is because: 1. `md5sum` is not a native macOS command (macOS equivalent is `md5`), 2. Homebrew's `md5sum` is typically in `/opt/homebrew/bin`, which is no longer in the restricted `PATH`. Since the repo already maintains a cross-platform `//tests/util:md5` tool, the fix simply consists in leveraging it. Note on: ```diff - cmd = "for i in $(OUTS); do echo 1 >$$i; done", + cmd = "for i in $(OUTS); do echo $$i >$$i; done", ``` ... is only meant to get distinct md5 sums for the 2 input files used in tests.
93cfdf1 to
2254f19
Compare
Contributor
Author
Collaborator
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.
Bazel 9.0.0 flipped
--incompatible_strict_action_envtotrueby default (bazelbuild/bazel#27670), restrictingPATHto/bin:/usr/bin:/usr/local/bin.On macOS, this broke a few tests relying on the
md5sumcommand (example):This is because:
md5sumis not a native macOS command (macOS equivalent ismd5),md5sumis typically in/opt/homebrew/bin, which is no longer in the restrictedPATH.Since the repo already maintains a cross-platform
//tests/util:md5tool, the fix simply consists in leveraging it.Note on:
... is only meant to get distinct md5 sums for the 2 input files used in the tests.
Fixes #1010.