feat(tags): create missing tags automatically; push tags with a scoped App token, no unsigned fallback - #369
Merged
Conversation
…d App token, no unsigned fallback The "refusing to allow a GitHub App to create or update workflow ... without workflows permission" error that blocked tags on older commits was a credential problem, not a platform limit: every tag-writing job checked out with the default GITHUB_TOKEN, actions/checkout persisted it, and git pushed with it. That token can never hold the workflows scope; the App token was only used for REST calls. - tag-health (orphaned releases, major/minor, bot signatures, unsigned, misaligned, orphaned tags): create the App token first, scoped to permission_contents + permission_workflows, and check out with it so pushes carry it. - publishing (create-release, update-version-tags, publish-extras) and sync-release-notes: same two scopes; checkout-code gains a token input and create-release / update-major-version-tags persist the App token. - tag/create: no REST fallback. A refused push throws, naming the tag and git's error; an unsigned tag is never created. Git calls use argv. fix-orphaned-releases drops its unsigned REST fallback too, and fix-unsigned-tags fails the job when a re-sign push is refused. - sync-release-notes: automatic runs create missing version tags at their release commits, bot-signed, with the changelog file as the verbatim message, capped by max_new_tags (default 20) per run; the rest are reported for the next run. Creating missing releases stays a dispatch switch (each new release fires release:published). - Tests: signed tag creation pushes a verified, heading-preserving tag; a refused push throws and makes no REST call and no tag. Refs #362
Shinrai
approved these changes
Oct 4, 2026
cldmv-bot Bot
added a commit
that referenced
this pull request
Oct 5, 2026
## 🚀 What's Changed ### 💥 Breaking Changes _No breaking changes_ ### ✨ Features - #369 - feat(tags): create missing tags automatically; push tags with a scoped App token, no unsigned fallback (214ae49) - #365 - feat(sync-release-notes): run automatically as part of the standard v4 set (006752d) ### 🐛 Bug Fixes - #365 - fix(tags): keep Markdown headings in tag messages (--cleanup=verbatim) (84227b7) ### 📦 Dependencies - #367 - deps: bump brace-expansion from 5.0.9 to 5.0.12 (85aaaec) ### 🔧 Other Changes - #366 - docs: add v4.30.7 release notes and a What's New block to the README (dc49336) - docs(changelogs): backfill every shipped v4 release without a changelog file (abcb453) <details> <summary>👥 Contributors</summary> - @Shinrai </details> <!-- co-authors --> Co-authored-by: Shinrai <Shinrai@users.noreply.github.com>
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.
🚀 What's Changed
💥 Breaking Changes
No breaking changes
✨ Features
🐛 Bug Fixes
No bug fixes
📦 Dependencies
No dependency updates
🔧 Other Changes
No other changes
👥 Contributors