Conversation
Replaces auto-tag + publish-npm + publish-pypi. Publishing now happens in the same run that creates the tag, so we no longer depend on a tag push triggering a separate workflow — which the default GITHUB_TOKEN can't do. No release PAT needed. Same model as lizard-cli's release.yml. npm keeps using NPM_TOKEN (no trusted publisher configured for the SDK); PyPI keeps using OIDC. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
mikelun
force-pushed
the
ci/single-release-workflow
branch
from
August 26, 2026 14:14
0a3cf9f to
bf47b11
Compare
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.
What
Replaces the three-workflow chain (
auto-tag→publish-npm/publish-pypi) with a singlerelease.ymlthat versions, tags and publishes both packages in one run — same model aslizard-cli.Why
auto-tagpushed the tag with the defaultGITHUB_TOKEN, and GitHub does not let that token trigger other workflows. So tagsv0.1.9..v0.1.12were created butpublish-npm/publish-pypinever ran — PyPI stuck at 0.1.8, npm at 0.1.7. Folding publish into the same run removes the trigger gap, so no release PAT is needed.Before you merge
lizard-sdk: workflow filenamepublish-pypi.yml→release.yml(ownerlizard-build, repolizard-sdk). Otherwise the PyPI step of the first run fails on OIDC. pypi.org → projectlizard-sdk→ Settings → Publishing.NPM_TOKENsecret is still valid — npm lagged a version behind PyPI, so the 0.1.8 npm publish likely failed.On merge
The workflow runs, bumps to v0.1.13 (last tag is v0.1.12) and publishes 0.1.13 to both registries — shipping the
lizard.builddefault fix. The bump commit is marked[skip ci]so it does not re-trigger.RELEASE_PATis no longer needed — no need to create it, and the earlier fallback went away withauto-tag.yml.Co-authored with Claude Opus 4.8.