Prepare tooling 0.7.1 release#373
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.
What type of PR is this?
documentation
What this PR does / why we need it:
Prepares the numbered tooling 0.7.1 release. It consolidates the fixes and refinements that landed on
mainsince v0.7.0:Changes:
VERSION.yaml→ 0.7.1, av0.7.1CHANGELOG.mdsection, and a README release-information tag touch-up. No new rule ID.Which issue(s) this PR fixes:
Fixes #
Special notes for reviewers:
Numbered release PR —
v1-rcis moved to the released commit after merge. Both regression canaries are green againstmain, so the gate is the same canary basis used for the 0.7.0 release (no manual E2E): the validation regression canary (11/11) covers the validation and linting changes, and the release-automation regression canary covers the #372 Review PR template change.Changelog input
Additional documentation
This section can be blank.