[jcary741]

Releases and the demo site deploy automatically from a single main branch, replacing the manual npm release and the Publisher deploy.

Running the workflow manually on a branch publishes a prerelease to npm and deploys the demo to labs staging.

Also fixes packaging: dist/ is gitignored and nothing built it before publish, so a publish from the repo would have shipped without its main entry. Adds "files": ["dist"] and a prepublishOnly compile (the tarball is now just LICENSE, README, dist/to-color.js and package.json). Bumps .nvmrc from 22 to 24 (npm Trusted Publishing needs Node 20.17+), and normalizes repository.url for npm provenance.

Blocked by https://github.com/mapbox/gitops-infra/pull/2814

TODO

Before merge:

• Configure Trusted Publishing for @mapbox/to-color on npmjs (workflow npm-release.yml, environment npm-release).
• Create the npm-release GitHub Environment in this repo.

After merging:

• Rename publisher-production to main; the workflow only runs on main.
• Delete the stale cloudplat-3162/add-npm-oidc-publish branch.
• Update branch protection.
• The first push to main deploys the demo to both labs sites. It publishes to npm only if a fix: or feat: commit came in.

[tristen]

Should this be publisher-production? main does not exist unless you are intended to change this but note we still want to publish builds to that branch

[jcary741]

Yep! That's in the post-merge TODO:

-[ ] Rename publisher-production to main; the workflow only runs on main.