Prepare tooling 0.8.1 release#396
Merged
Merged
Conversation
Contributor
Author
|
Moved v1-rc in interim already to head of main branch (to provide the fix for camaraproject/QualityOnDemand#575). Will be moved to the release PR commit when it landed. |
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.8.1 patch release. It consolidates the fix that landed on
mainsincev0.8.0:#comment documenting the raw operation being misread as a scenario step (fix(validation): fix two P-025 false positives on real-world feature-file lines #395)Changes:
VERSION.yaml→ 0.8.1, av0.8.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. Validation Regression canary is green 11/11 at HEAD (run 30030628357). No RA-scope files changed sincev0.8.0, so the RA Regression canary basis is unchanged — no manual E2E needed.Changelog input
Additional documentation
This section can be blank.