Found while working #57 (PR #58); filed rather than folded in, since it touches ~38 files across every package and is unrelated to the rjsf peer range.
What
The repository now lives at i2mint/acture — github.com/thorwhalen/acture is a redirect (gh repo view thorwhalen/acture --json nameWithOwner → i2mint/acture). But the repo's own metadata still names the old owner in 73 places across 38 files, including every publishable package's repository.url, homepage, and bugs:
"repository": { "url": "git+https://github.com/thorwhalen/acture.git", "directory": "packages/…" },
"homepage": "https://github.com/thorwhalen/acture#readme",
"bugs": "https://github.com/thorwhalen/acture/issues"Those three strings are what npm renders as the Repository / Homepage / Issues links on each of the 19 package pages, and they are baked into every published tarball. GitHub's redirect keeps them working today; it stops working the moment anyone creates a new repo at thorwhalen/acture.
Why it is worth a pass
- npm provenance / trusted publishing matches on the repository URL. If the release workflow ever moves to OIDC trusted publishing, a stale
repository.url is the field that has to be right.
gh gets confused by it in practice: gh pr create --repo thorwhalen/acture from a checkout whose origin is git@github.com:thorwhalen/acture.git fails with No commits between i2mint:main and thorwhalen:<branch> — it resolves the base through the redirect and the head without it. gh repo set-default thorwhalen/acture likewise reports "does not correspond to any git remotes". Everyone hitting this has to work out the redirect first.
Scope
Mechanical: rg -l 'github.com/thorwhalen/acture' → 38 files (all 19 packages/*/package.json, the root and per-package READMEs, AGENTS.md, docs, skills). Worth checking the git remote in local clones too, and whether scripts/sync-python-version.mjs / the PyPI metadata carry the same string.
Cosmetic-until-it-isn't, so no urgency — but it is a one-commit sweep and it only gets more expensive as the docs grow.
Found while working #57 (PR #58); filed rather than folded in, since it touches ~38 files across every package and is unrelated to the rjsf peer range.
What
The repository now lives at
i2mint/acture—github.com/thorwhalen/actureis a redirect (gh repo view thorwhalen/acture --json nameWithOwner→i2mint/acture). But the repo's own metadata still names the old owner in 73 places across 38 files, including every publishable package'srepository.url,homepage, andbugs:Those three strings are what npm renders as the Repository / Homepage / Issues links on each of the 19 package pages, and they are baked into every published tarball. GitHub's redirect keeps them working today; it stops working the moment anyone creates a new repo at
thorwhalen/acture.Why it is worth a pass
repository.urlis the field that has to be right.ghgets confused by it in practice:gh pr create --repo thorwhalen/acturefrom a checkout whoseoriginisgit@github.com:thorwhalen/acture.gitfails withNo commits between i2mint:main and thorwhalen:<branch>— it resolves the base through the redirect and the head without it.gh repo set-default thorwhalen/acturelikewise reports "does not correspond to any git remotes". Everyone hitting this has to work out the redirect first.Scope
Mechanical:
rg -l 'github.com/thorwhalen/acture'→ 38 files (all 19packages/*/package.json, the root and per-package READMEs,AGENTS.md, docs, skills). Worth checking thegit remotein local clones too, and whetherscripts/sync-python-version.mjs/ the PyPI metadata carry the same string.Cosmetic-until-it-isn't, so no urgency — but it is a one-commit sweep and it only gets more expensive as the docs grow.