Repository navigation
Align maintenance checks and Windows release packaging - #17
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.
PR checks now verify preview pixels and build the complete release packages on all six OS/Node combinations before merge. Dependabot checks Python build tools and GitHub Actions weekly; official actions are updated and pinned to immutable commits.
Pages resolves only a published release and stops on lookup failure. Checks run once per PR or main update, with cancellation of superseded checks and bounded job runtimes. Release tag/version and main-ancestry requirements remain enforced. Contributor guidance derives the tag from package metadata.
Validation: all eight contributor checks passed, including 49 runtime tests; actionlint and YAML/configuration checks passed; simulated release lookup failure stops deployment; matching tags pass and mismatched tags fail.
These maintenance changes do not alter runtime behavior or retag existing releases.
The new Windows packaging check exposed a real UTF-8 changelog decoding failure. The release builder now explicitly reads metadata/changelog text as UTF-8 and writes notes/checksums with UTF-8 and LF newlines. All six builders passed a full package build under a simulated cp1252 default; the required CI repeats the real Windows check.