Repository navigation
ci: publish and release with the org CASE_PKG_WRITE secret - #22
Merged
Merged
Conversation
The repo GITHUB_TOKEN lacks write_package on @smallcase/bite, so tag publishes for 3.2.0, 3.2.1 and 3.3.0 failed with 403. Use the org package token for publishing and release-please, and allow manually dispatching the publish workflow to retry a failed release. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
khusharth
approved these changes
Oct 12, 2026
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.
Problem
The
v3.3.0release was tagged, but the publish job failed:The workflow publishes with the repo
GITHUB_TOKEN, which has no write access to the@smallcase/bitepackage. Thev3.2.0andv3.2.1publish runs failed the same way. The registry'slatestis still3.2.1.Change
publish.yml: publish with the orgCASE_PKG_WRITEsecret, as sc-fe-components does, and addworkflow_dispatchso a failed release can be published again.release-please.yml: useCASE_PKG_WRITEinstead of the repoPAT.test.yml: unchanged; bite has no private dependencies to read.CASE_PKG_WRITEisn't shared with sc-fe-bite yet. OnlyCASE_PKG_READis visible to this repo. An org admin needs to addsc-fe-biteto the secret's repository access. Otherwise the token is empty and release-please fails on the merge commit.After merging
Run Publish to GitHub Packages manually on
master(Actions → Run workflow).masteris still at version3.3.0, and this PR only changes workflows, so the published package matches thev3.3.0tag apart from CI files.🤖 Generated with Claude Code