Skip to content

Fix stale GitHub Packages references after npmjs migration #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kin0992 merged 1 commit into from
Jun 1, 2026
Merged

Fix stale GitHub Packages references after npmjs migration #39

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .changeset/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,4 +14,4 @@ Pick the changed packages, the bump type (`patch` / `minor` / `major`), and writ

1. PRs include changeset files.
2. On merge to `main`, the `release` workflow opens (or updates) a "Version Packages" PR that bumps versions and updates `CHANGELOG.md` for each package.
3. Merging that PR publishes the affected packages to GitHub Packages and creates GitHub Releases.
3. Merging that PR publishes the affected packages to npmjs.org (public, with provenance) and creates GitHub Releases.
2 changes: 1 addition & 1 deletion .npmrc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
@kin0992:registry=https://npm.pkg.github.com
@kin0992:registry=https://registry.npmjs.org