Repository navigation
Conversation
* ci: enforce the minor-version parity instead of documenting it "0.19.x means implements spec 0.19" lived only in prose, which left it one typo from being silently false: a changelog heading naming 0.20.0 against a spec still at 0.19, or an implementation of 0.20 released as 0.19.4, and nothing anywhere would have failed. This repo now carries a SPEC_VERSION file naming the spec it implements, and check-version-parity.sh asserts two things in CI: the changelog's minor equals it, and every Utos.* package pin is on that same minor. A package on a different minor is on a different spec line, so a release claiming 0.19 while depending on 0.20 packages is refused. Checked at PR time rather than at release time, because at release time the mistake is a tag and a published artifact that cannot be taken back. Both halves verified by breaking them. * ci: mark check-version-parity.sh executable Windows git does not record the file mode, so chmod +x locally left it 100644 in the index and the CI step failed with 'Permission denied' before it could check anything. Set with git update-index --chmod=+x, which is mode-only and independent of the filesystem.
) They explained why YAML is read through YamlDotNet's node graph rather than its object deserializer -- true while the source-format mapping lived here, and untrue since 0.19.0 moved it to Utos.Workflow.Source. The unused YamlDotNet pin went with them. Central package management kept the version and its rationale alive after the last PackageReference was deleted, so nothing failed to tell us it was dead. The notes now say what is true: neither reading a document nor judging a bundle is implemented here, both live in packages every tool shares, and that is what keeps a workflow one tool accepts from being one another rejects.
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.
Back-merge, not a release.
[Unreleased]carries no date, sorelease.ymlresolves0.19.0, finds the tag and skips — the path its own comment describes as "main also receives pushes that are not releases — a docs fix, a back-merge."0.19.0stays current, which is a true statement about what this repo supports: nothing here changed behaviour. The notes ride the next real release.Lands on the default branch: the corrected design notes (#26), the removed dead
YamlDotNetpin, and the parity enforcement (#25, #27). The README GitHub shows is currently the one describing a dependency the CLI no longer has.