@indigoai/indigo-icons 0.3.3 → 0.3.4

package/README.md

@@ -22,7 +22,23 @@ docker compose run --rm frontend ./publish_local.sh
 
 ## Publishing the package to NPM
 
-You should have an NPM account and be logged in to publish the package.
+Releases are published from GitLab CI, not from a laptop:
+
+1. Bump `version` in `package.json` on `main` and push a tag `vX.Y.Z` on that commit. The tag's `version` job fails
+   when the two don't match: fix `package.json`, commit, then delete the tag and push it again on the new commit.
+2. Once `version` passes, the `npm` job publishes the package without waiting for anyone.
+3. The job publishes through npm trusted publishing, so GitLab holds no npm token. On npmjs.com, the package
+   (Settings → Trusted publishing → GitLab CI/CD) trusts namespace `indigo.ai`, project `design-system-icons`, CI file
+   `.gitlab-ci.yml`, with no environment. It works only on GitLab.com shared runners. The package is published
+   without npm provenance, which needs a public source repository.
+
+A version with a pre-release suffix (`vX.Y.Z-rc.N`) is published under the `next` dist-tag, so it never becomes
+`latest`.
+
+### Legacy: publishing manually
+
+Before the pipeline, the package was released from a laptop. This still works but is superseded by the tag
+pipeline above. You need an NPM account with publish rights and to be logged in.
 
 Bump the package version, manually or using one of the npm commands: npm version patch, npm version minor, npm
 version major. Then run:

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@indigoai/indigo-icons",
   "description": "Indigo Icons",
-  "version": "0.3.3",
+  "version": "0.3.4",
   "type": "module",
   "license": "MIT",
   "exports": {