Fix CI test failure and add GitHub Packages publishing#161
Merged
that-github-user merged 3 commits intomainfrom Mar 31, 2026
Merged
Fix CI test failure and add GitHub Packages publishing#161that-github-user merged 3 commits intomainfrom
that-github-user merged 3 commits intomainfrom
Conversation
- Fix exit-127 preflight test: accept both "Test command not found" and generic failure message (Linux returns 127, Windows may differ) - Add GitHub Packages publish step to release workflow: publishes as @that-github-user/thinktank-ai to npm.pkg.github.com alongside the existing npmjs.org publish - Add packages:write permission to release workflow Fixes CI failure from #160. Resolves "No packages published" on GitHub. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.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
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.
Summary
Details
CI fix: The
returns warning when command is not foundtest expected"failed on the current branch"but our exit-127 fix (from the test runner improvements) changed the message to"Test command not found". Test now accepts either message.GitHub Packages: The repo shows "No packages published" because we only publish to npmjs.org. Added a second publish step that:
.npmrcfornpm.pkg.github.com@that-github-user/thinktank-ai(required by GitHub Packages)GITHUB_TOKENauthpackages:writepermissionTest plan
npm testpasses locally (250 tests)v*tag triggers both npm and GitHub Packages publish🤖 Generated with Claude Code