Repository navigation
chore(vale): pin Vale 3.19.0 - #223
Merged
Merged
Conversation
github-actions
Bot
added
the
skip-changeset
theCodeDrift
added a commit
that referenced
this pull request
Sep 1, 2026
Bumps the six `@taskless/vale-*` pins from 3.18.0-20260824195610 to 3.19.0-20260901000817, the stamp release-vale.yml minted on the push to main that merged #223. This is the commit the rest of the branch was waiting on. Everything else here was measured against a 3.19.0 binary fetched from upstream and verified against the manifest digest; the vendor contract could not agree, because the installed package was still 3.18.0 and the contract refuses to certify a claim against a binary other than the pinned one. That refusal is the guard working, and it is why this branch was a draft. The whole suite now runs against the published binary rather than a hand-placed one: the pinned-version assertion and the two new `.ex`/ `.exs` probes pass on the artifact a user will actually install.
theCodeDrift
added a commit
that referenced
this pull request
Sep 1, 2026
Bumps the six `@taskless/vale-*` pins from 3.18.0-20260824195610 to 3.19.0-20260901000817, the stamp release-vale.yml minted on the push to main that merged #223. This is the commit the rest of the branch was waiting on. Everything else here was measured against a 3.19.0 binary fetched from upstream and verified against the manifest digest; the vendor contract could not agree, because the installed package was still 3.18.0 and the contract refuses to certify a claim against a binary other than the pinned one. That refusal is the guard working, and it is why this branch was a draft. The whole suite now runs against the published binary rather than a hand-placed one: the pinned-version assertion and the two new `.ex`/ `.exs` probes pass on the artifact a user will actually install.
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
1 participant
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.
Stack (root → tip):
Upstream Vale is ahead of the version this repository packages.
This updates
.github/scripts/vale-manifest.jsonto the new upstreamversion and replaces every platform's SHA256 with the digest from
upstream's
vale_<version>_checksums.txt.Reviewing this is the trust boundary. Merging it authorizes the
publish phase to download those exact archives and package them; a
download that does not match a digest here aborts the run and
publishes nothing. Check the digests against upstream's checksums file
for the release before approving.
Merging this triggers the publish phase, which stamps every platform
package
<valeVersion>-<yyyymmddhhmmss>and publishes the set. Thatpublish is inert on its own:
@taskless/clipins exact versions, sonothing reaches a consumer until that pin is deliberately bumped.