From 752a42a832775534ca8dada000ae69d1c0915c31 Mon Sep 17 00:00:00 2001 From: Marco Comi <9998393+kin0992@users.noreply.github.com> Date: Mon, 1 Jun 2026 23:19:15 +0200 Subject: [PATCH] Fix stale GitHub Packages references after npmjs migration The repo publishes to npmjs.org since #36, but the @kin0992 scope in .npmrc still routed to GitHub Packages and the changeset README still described the old publish target. Co-Authored-By: Claude Opus 4.8 --- .changeset/README.md | 2 +- .npmrc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.changeset/README.md b/.changeset/README.md index f08a37e..0cc856a 100644 --- a/.changeset/README.md +++ b/.changeset/README.md @@ -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. diff --git a/.npmrc b/.npmrc index 7d7d3cb..1e18057 100644 --- a/.npmrc +++ b/.npmrc @@ -1 +1 @@ -@kin0992:registry=https://npm.pkg.github.com +@kin0992:registry=https://registry.npmjs.org