chore: publish under the @crunchloop scope#2
Merged
Conversation
Rename to @crunchloop/ghostty-web so the package publishes to the crunchloop-owned npm scope (the upstream `ghostty-web` name isn't ours). publishConfig already pins access: public, and the publish workflow's --provenance + OIDC trusted publishing works for scoped public packages. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- test: use the lib-scoped `bun run test` instead of bare `bun test`. Bare `bun test` also collected the Playwright e2e specs (9 "Playwright Test did not expect test.describe()" errors); the 434 lib tests already pass. - build: raise the WASM size guard 512 KB -> 1 MB. The pinned ghostty now produces a ~625 KB ReleaseSmall wasm, which tripped the stale 512 KB check. - fmt: format docs/superpowers/plans/2026-05-24-e2e-playwright-coverage.md. Co-Authored-By: Claude Opus 4.8 (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
Rename
ghostty-web→@crunchloop/ghostty-webso the package publishes to thecrunchloop-owned npm scope (the upstream name isn't ours).
publishConfig.access: public+ the workflow'snpm publish --provenancealready support scoped-publicpublishing via OIDC trusted publishing (no npm token / GitHub secret needed).
Follow-up (needs
workflowtoken scope — not in this PR)The
publish-demojob in.github/workflows/publish.ymlpublishes@ghostty-web/demo(a scope we don't own) and will turn the workflow run redeven when the main publish succeeds. It should be removed, but editing workflow
files requires a token with the
workflowscope. Do it via the GitHub UI, orgrant the scope locally (
gh auth refresh -h github.com -s workflow) and it canbe pushed.
Before first publish
Configure a Trusted Publisher on npmjs.com for
@crunchloop/ghostty-web→GitHub Actions →
crunchloop/ghostty-web/publish.yml. Then merge tomain(publishes a
nextprerelease) or tagv*(stable).🤖 Generated with Claude Code