refactor: rename npm scope @cacheplane → @ngaf; drop mcp from publishable group#145
Merged
Conversation
Bulk find/replace across 536 files (88 package.json, 15 tsconfig paths, 448 source files). Drop packages/mcp from publishable group (private:true) for first release; defer mcp to a future release. After the rename merges, user manually publishes 0.0.1 of the 7 packages, then a separate PR switches the workflow to npm trusted publishing (no token needed). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
5 tasks: pre-flight audit (verify @Ngaf is claimable on npm), bulk find/replace across 536 files, drop mcp from publishable group with private:true, lockfile reconciliation, final verify + PR. Plus documented post-merge flow for first manual publish + trusted publishing migration. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Bulk rewrite of 434 references (88 package.json, 15 tsconfig paths, 331 source files + READMEs). Excludes apps/minting-service/ and docs/superpowers/ historical artifacts. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The MCP integration package isn't ready for first release. Mark packages/mcp 'private: true' so it can't accidentally publish, and remove from the synchronized publishable release group. Re-add when the package matures. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
4 tasks
blove
added a commit
that referenced
this pull request
May 1, 2026
PR #145 (the @cacheplane → @Ngaf scope rename) missed apps/minting-service. Imports of @cacheplane/db and @cacheplane/licensing no longer resolve because the path aliases were renamed to @ngaf/*; every Vercel preview deploy of cacheplane-minting-service has been failing as a result. This commit: - renames the package itself from @cacheplane/minting-service to @ngaf/minting-service - updates the 8 import sites in handlers, src/lib, scripts to @ngaf/db and @ngaf/licensing - updates @cacheplane/* references in build.mjs comments - mirrors the package rename in package-lock.json (surgical edit, not regenerated) Verified: `npx nx build minting-service` succeeds; `npx vitest run` passes 42/42 in apps/minting-service. Co-authored-by: Claude Opus 4 <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
Motivation
`@ngaf` (Angular Agent Framework, abbreviated) is short (5 chars vs 24-char alternative), pronounceable, and identifies the project rather than the parent company. npm package names are sticky once published — better to rename now, before the first release. Pre-flight registry check confirmed `@ngaf/*` returns 404 (scope appears claimable; final verification at first-publish time).
Final publishable set
Test Plan
Pre-existing failures (not caused by this PR)
`nx affected -t build` flags 3 builds as failing: `cockpit-docs`, `ui-react`, `minting-service`. Verified these fail identically on `origin/main`; they are NOT introduced here.
What this does NOT do
Design + plan
🤖 Generated with Claude Code