Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(bzlmod): mark toolchains extension as reproducible #970

Merged
merged 1 commit into from
Dec 11, 2024

Conversation

cerisier
Copy link
Contributor

@cerisier cerisier commented Oct 21, 2024

Marking the toolchains extension as reproducible since all underlying tools are already checked for integrity. Saving an entry in the lockfile for that extension.

Marking this has to be conditional to bazel_features.external_deps.extension_metadata_has_reproducible, hence bumping bazel_features to 1.9.0 which is the version introducing the check (https://github.com/bazel-contrib/bazel_features/releases/tag/v1.9.0)

Copy link
Collaborator

@alexeagle alexeagle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome thanks!

@alexeagle
Copy link
Collaborator

@cerisier it seems you didn't allow maintainers to push to your PR branch, so I can't rebase this for you to pick up the updated GHA workflow that satisfies our required check. Could you rebase to current HEAD pls?

@alexeagle alexeagle enabled auto-merge (squash) December 6, 2024 17:27
auto-merge was automatically disabled December 7, 2024 16:21

Head branch was pushed to by a user without write access

@cerisier cerisier force-pushed the reproducible-extension branch from 8557ef4 to a16fe8f Compare December 7, 2024 16:21
@cerisier
Copy link
Contributor Author

cerisier commented Dec 7, 2024

@alexeagle done !

@alexeagle alexeagle merged commit 1549b1f into bazel-contrib:main Dec 11, 2024
22 checks passed
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.

2 participants