Repository navigation
ci(validation): add pull request release checks - #10
Merged
Merged
Conversation
DimitryZH
marked this pull request as ready for review
October 20, 2026 13:07
13 tasks done
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
Add pull request and main-push validation with separate installed-package regression and new-release eligibility checks.
Changes
Validation
All 60 local automated tests and clean-wheel checks passed, including the expected 12 baseline legacy failures. Git diff whitespace checks passed. GitHub Actions run: Python 3.11 and 3.13 tests/package checks passed; Release check passed with explicit no_candidate_changes. Logs inspected.
Limitations
Required checks and review ownership need owner configuration. Historical baseline remains ineligible; Compose and deployment are outside scope.
Related to #9