Repository navigation
ci: publish versioned Vale packages automatically - #378
Merged
Merged
Conversation
brendanclement
marked this pull request as ready for review
October 19, 2026 17:33
geruh
reviewed
Oct 19, 2026
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
2 participants
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.
Build and publish the shared Vale package automatically when a version change merges into main. This PR changes only the workflow and release instructions; there is no custom Python helper or release-test suite.
The workflow keeps the existing Vale rule tests and builds the ZIP on Ubuntu. PR runs cannot publish. Main publishes new versions; an existing version is skipped only after its tagged package source and unpacked download match. Different or incomplete releases fail without being overwritten.
Version 0.1.0 is already published. Merging this workflow verifies it and skips publication. Consumer repositories still adopt new versions explicitly. This releases the style package, not the documentation site.
Validation: the simplified packaging step checked the actual v0.1.0 tag and download locally and skipped publication successfully. Shell syntax and YAML were checked. Hosted validation caught platform-dependent ZIP timestamps; comparison now uses unpacked files. Hosted PR packaging runs on each update; actual upload remains restricted to main.