Closed
Conversation
juanzolotoochin
approved these changes
Jun 12, 2025
nickvines
force-pushed
the
20250612-fips
branch
4 times, most recently
from
2e08b3e to
8ccb73d
Compare
nickvines
force-pushed
the
20250612-fips
branch
2 times, most recently
from
43b4c52 to
75f78ee
Compare
…s, justfile, release on PRs
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.
This PR tracks the 20250612-fips branch. This should not be merged.
First commit updates:
Second commit:
Future releases - make a new branch off this one, rebase off main, make PR, then launch the release workflow after all checks complete on that PR.
See Bazel Playbook