chore(release): prepare v0.2.0 - #150
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
Cargo.lockto0.2.0v0.2.0release notesWhy
The v0.2 editor surface is complete and the final repository, code, performance, terminal, security, packaging, and Nightly audits are clean. This prepares the next stable release without including unfinished v0.3 roadmap items.
Verification
cargo fmt --all -- --checkgit diff --checkcargo test --all-targets(317 unit tests and 5 signal-cleanup tests)cargo test --all-targets -- --ignored(4 performance tests)cargo clippy --all-targets --all-features -- -D warningscargo build --all-targetscargo build --release --target aarch64-apple-darwinactionlint1.7.12 on the release workflowcortex 0.2.0Release plan
After this PR merges with protected CI green, tag the exact merge commit as
v0.2.0. Wait for the tag-triggered Release workflow, then verify the archive, checksum, signed provenance, architecture, release notes, installer resolution, and binary version.