Don't trigger releases for ABI-suffixed tags - #142
Merged
Conversation
Tags like v0.25.0-abi14 are used to publish ABI 14 regenerations of the grammar for editors stuck on tree-sitter 0.24 (e.g. Homebrew Emacs 30 on macOS). Cutting such a tag currently fires the publish workflow, pushing duplicate releases to NPM, crates.io and PyPI. Exclude '*-abi*' tags from the trigger so these markers can be tagged safely.
314eter
pushed a commit
that referenced
this pull request
Jun 22, 2026
Tags like v0.25.0-abi14 are used to publish ABI 14 regenerations of the grammar for editors stuck on tree-sitter 0.24 (e.g. Homebrew Emacs 30 on macOS). Cutting such a tag currently fires the publish workflow, pushing duplicate releases to NPM, crates.io and PyPI. Exclude '*-abi*' tags from the trigger so these markers can be tagged safely. (cherry picked from commit 527d62e)
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.
Picking up the thread from #141. The reason an ABI 14 tag for v0.25.0 never got cut is that any tag push fires the publish workflow and would push duplicate releases to NPM, crates.io and PyPI.
This excludes
*-abi*tags from the trigger, so a tag likev0.25.0-abi14can be created as a plain GitHub marker (and a place to attach an ABI 14 regeneration) without re-publishing the packages.I think this approach would be preferable for consumers of the grammar over an
abi14branch and doesn't add much maintenance overhead.Fixes #141