feat(releases): add Cargo crate evidence profile - #52
Merged
Conversation
Pull Request Summary by devActivityMetricsAchievements
|
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.
Closes #50.
What this adds
cargo-craterelease profile for Cargo package distributionegohygiene.relay-cargo-crate-release/v1evidence contract<package>-<version>.cratearchive and SHA-256 agreementCompiled Rust binaries intentionally remain under Relay's distinct
binaryprofile. A project shipping both a crate and executables composes two independently reviewable bundles.Validation
Ruby is unavailable in the local workspace, so the repository's required CI gate remains responsible for parsing GitHub Actions YAML.
After this merges, the next dependency-correct task is #47: reusable semantic-release workflows.