Repository navigation
Release aggr 2.0.0 and establish v2 workflow channel - #55
Merged
Merged
Conversation
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.
Summary
main.@v2reusable workflow and generated instance workflow. The existing@v1tag continues to select v1 binaries.Test plan
cargo test --bin aggr commands::init::tests::the_shipped_snippets_are_validpassed.cargo fmt --all -- --check,actionlint, andgit diff --checkpassed.make checkran out of disk space during Rust compilation; the PR CI matrix will provide full validation.Release plan
After this PR passes CI and merges, tag the merge commit
v2.0.0. Once all six release binaries and checksums are published, create the stablev2workflow tag and migrate the instance to@v2with the new config keys.