docs: update stale cliff.toml leading comment - #19
Merged
Conversation
The header described a two-cliff-invocation design referencing `auto-tag.yaml` (renamed to `auto-release.yaml`) and `--bumped-version` (replaced by `--bump --context` + jq parsing). PR #13 consolidated the two invocations into a single `--unreleased --bump --context` call that emits JSON the workflow then re-renders with `--from-context`. The comment never caught up.
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.
Why
The cliff.toml leading comment described a two-cliff-invocation design that hasn't matched reality since PR #13:
auto-tag.yaml-- renamed toauto-release.yamllong ago.--bump --context+ jq parsing.Pure doc fix. No behavior change.
Bonus: catch-up trigger for PR #18
After PR #18 merged, GitHub Actions did not register a workflow run for the merge commit `d128ff7` (no `github-actions` check-suite, no workflow_run record). v1.5.0 was never created. Pushing this small `docs:` commit on top of `d128ff7` should re-arm the dispatcher and let `--unreleased --bump` see BOTH the unreleased `feat:` from #18 AND this commit, computing v1.5.0 (minor bump from feat). Expected result on merge:
If that all happens, the design is validated end-to-end and the muster #795 + agentic-platform/-mcps migration PRs can move forward with confidence.