gmackie/ForgeGraph
1
0
Fork 0
Code Issues 8 Pull requests 10 Projects Releases Packages Wiki Activity Actions

chore(registry): name the npm registry service for what it is #602

Open
gmackie wants to merge 1 commit from registry-rename into main
pull from: registry-rename
merge into: gmackie:main
Conversation 1 Commits 1 Files changed 1 +1 -1
gmackie commented 2026-09-24 13:45:30 +00:00
Owner
Copy link

apps/registry declared itself @forgegraph/registry, which now collides with a published package of that name — the Forge compiler's artifact signing and catalog library, on npm since 0.3.0.

Nothing breaks today because this one is private: true and never published. But two packages cannot share a name in one workspace, and these repositories are meant to converge.

The name was inaccurate anyway

This is a Verdaccio-based npm registry serving npm.forgegraf.com — not "the ForgeGraph registry". Its own ForgeGraph app slug has been npm-registry all along, so @forgegraph/npm-registry both says what it is and matches the slug.

Why this side

Cost, not seniority. A published package cannot be unpublished, only deprecated, and that one has dependents. Renaming the private app is one line; renaming the published library would strand a version on npm and every install already pointing at it.

Blast radius

One file. The only place in the repository that mentioned the old name was its own package.json — no imports, no workflow paths, no lockfile entries. pnpm install --frozen-lockfile and turbo typecheck both pass.

`apps/registry` declared itself `@forgegraph/registry`, which now collides with a published package of that name — the Forge compiler's artifact signing and catalog library, on npm since 0.3.0. Nothing breaks today because this one is `private: true` and never published. But two packages cannot share a name in one workspace, and these repositories are meant to converge. ## The name was inaccurate anyway This is a Verdaccio-based npm registry serving `npm.forgegraf.com` — not "the ForgeGraph registry". Its own ForgeGraph app slug has been `npm-registry` all along, so `@forgegraph/npm-registry` both says what it is and matches the slug. ## Why this side Cost, not seniority. A published package cannot be unpublished, only deprecated, and that one has dependents. Renaming the private app is one line; renaming the published library would strand a version on npm and every install already pointing at it. ## Blast radius One file. The only place in the repository that mentioned the old name was its own `package.json` — no imports, no workflow paths, no lockfile entries. `pnpm install --frozen-lockfile` and `turbo typecheck` both pass.
chore(registry): name the npm registry service for what it is
All checks were successful
CI / gitleaks (pull_request) Successful in 10s
Details
CI / storybook (pull_request) Successful in 2m56s
Details
CI / web-build (pull_request) Successful in 4m46s
Details
forgegraph/ci CI passed
CI / ci (pull_request) Successful in 13m3s
Details
41f92c9cb6 
apps/registry declared itself @forgegraph/registry, which now collides with a
published package of that name — the Forge compiler's artifact signing and
catalog library, on npm since 0.3.0. Nothing breaks today because this one is
private and never published, but the two cannot coexist in a single workspace,
and those repositories are meant to converge.

The name was inaccurate anyway. This is a Verdaccio-based npm registry serving
npm.forgegraf.com, not "the ForgeGraph registry"; its own ForgeGraph app slug
has been npm-registry all along. @forgegraph/npm-registry says what it is and
matches the slug.

The rename costs nothing to make: the package is private, and the only file in
the repository that mentioned the old name was its own package.json — no
imports, no workflow paths, no lockfile entries. Install and typecheck pass.

Which way to resolve it was decided by cost rather than seniority: a published
package cannot be unpublished, only deprecated, and this one has dependents.
Renaming the private app is a line; renaming the published library would strand
a version on npm and every install that already points at it.
gmackie commented 2026-09-24 13:52:04 +00:00
Author
Owner
Copy link

Preview environment is live: https://pr-602-forgegraph.forgegraf.com

Deployed 41f92c9c with the beta stage's environment. It redeploys on every push and is destroyed when this PR closes.

Preview environment is live: https://pr-602-forgegraph.forgegraf.com Deployed `41f92c9c` with the beta stage's environment. It redeploys on every push and is destroyed when this PR closes.
All checks were successful
CI / gitleaks (pull_request) Successful in 10s
Required
Details
CI / storybook (pull_request) Successful in 2m56s
Details
CI / web-build (pull_request) Successful in 4m46s
Details
forgegraph/ci CI passed
CI / ci (pull_request) Successful in 13m3s
Required
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin registry-rename:registry-rename
git switch registry-rename
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
community
Community process, governance, contribution UX

  
docs
Documentation improvements

  
forgegraph:public-update
Publish approved PR lifecycle updates to the ForgeGraph public feed.

  
good first issue
Suitable for first-time contributors

  
help wanted
Extra attention is needed; maintainers welcome a PR

No labels
community
docs
forgegraph:public-update
good first issue
help wanted
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
gmackie/ForgeGraph!602
No description provided.