Closed
Conversation
Co-authored-by: phlax <454682+phlax@users.noreply.github.com>
This was referenced Sep 7, 2026
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.
modules/sequoia-sqregistry metadata and versioned module filessequoia-sq1.4.0 source archive with verified integrity and overlay hashes@sequoia-sq//:sqtargetThis module follows the source-build path using
rules_rustandcrate_universe, selecting the pure-Rust Sequoia crypto backend (crypto-rust) so thesqbinary can be built without shipping custom, non-verifiable upstream binaries. The registry entry pinssequoia-sqat1.4.0.envoyand keeps theenvoyproxy/toolshedbazel/pgp/extensions.bzlintegration point intact until it can be simplified to consume@sequoia-sq//:sqviabazel_depinstead of downloading release artifacts itself.