Repository navigation
chore: rename browser-toolset to @stuntkit/browser-toolset, published to npm - #49
Conversation
…h to npm The package moves from GitHub Packages to npm under the stuntkit scope, ahead of the stuntdouble Studio repo move. Its version stays at 0.2.1 (the same code already on GitHub Packages); npm gets it first. The first npm publish is manual, because npm trusted publishing can only be configured for a package that already exists. Then the release workflow publishes later versions. Signed-off-by: Michael Parker <michael@stuntdouble.io>
d9b6cfb to
97a5c58
Compare
mrprkr
changed the title
![graphify-labs[bot]](https://avatars.githubusercontent.com/in/4356270?s=60&v=4){kind=small}
There was a problem hiding this comment.
Graphify reviewed this change.
Code graph out of date: Health delta baseline: last indexed commit 56f6b8e (diverged from this PR's base — delta is approximate). Impact and hotspot numbers below may be wrong.
No verdict: the code graph is out of date. Static checks found no blocking issues, but they compared against an outdated graph. The next push after the repository re-indexes gets a full review.
Not checked: tests were not run; no formal proof of the changed code.
No blocking issues. I didn't find anything I'd hold the merge for.
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 0 functions depend on the 0 functions this change touches.
Health — grade A; no new coupling hotspots.
Verification — 0 functions in the blast radius were not formally verified this run (proofs are advisory here).
Health delta baseline: last indexed commit 56f6b8e (diverged from this PR's base — delta is approximate).
Diff could not be reliably attributed to this PR: the base/head merge-base was unreachable in the shallow clone, so detailed findings were skipped (rather than emit a two-dot diff, which would misattribute base-branch changes).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Summary
Renames
@stunt-double/browser-toolsetto@stuntkit/browser-toolsetand moves it from GitHub Packages to npm, with provenance. Version stays at 0.2.1, the same code already on GitHub Packages. Thestuntkitnpm org is registered to the maintainer..changesetignore list use the new name.scripts/publish-npm.mjspublishesbrowser-toolsetalongsidestuntdouble.@stunt-double/*packages are unchanged and stay on GitHub Packages.Rollout (needs Michael)
cd packages/browser-toolset && pnpm build && npm publish --access public --provenance=false(2FA).npm trust github @stuntkit/browser-toolset --repo stunt-double/stuntkit --file release.yml --allow-publish(2FA).Verification
pnpm -r type-check,pnpm lint,pnpm format:check,pnpm test(all six suites, 0 failures)npm pack --dry-runinpackages/browser-toolset:@stuntkit/browser-toolset@0.2.1Risk
Anyone installing
@stunt-double/browser-toolsetfrom GitHub Packages must switch to the npm name. Known users today are the monorepo mirror and Studio.