ci: publish with NPM_TOKEN PAT (job GITEA_TOKEN cannot write org packages)

.gitea/workflows/ci.yaml

@@ -35,6 +35,9 @@ jobs:
     if: startsWith(github.ref, 'refs/tags/v')
     needs: check
     runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
     steps:
       - name: Checkout
         uses: actions/checkout@v4
@@ -55,4 +58,4 @@ jobs:
       - name: Publish
         run: npm publish
         env:
-          NODE_AUTH_TOKEN: ${{ secrets.GITEA_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 0.5.1
+
+- `QuestMetrics` / `reportProgress`: custom free-text metrics no longer
+  progress quests. Report a released catalog counter slug instead.
+  `purchaseOffer` / `purchaseItem` helpers are unchanged (server-side shop
+  fan-out).
+
 ## 0.5.0
 
 - `client.auth.loginWithCustom({ customData, region?, language?, nickname? })`

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rudder/js-sdk",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "publishConfig": {
     "registry": "https://hub.rudder.build/api/packages/rudder/npm/"
   },

src/quests/QuestMetrics.ts

@@ -3,8 +3,9 @@
  *
  * Purchase metrics are reported automatically server-side by the shop
  * purchase fan-out, so these helpers exist mainly to name the format
- * instead of hardcoding it. Any other metric is a custom string reported via
- * {@link QuestsService.reportProgress}.
+ * instead of hardcoding it. Catalog counter slugs are reported via
+ * {@link QuestsService.reportProgress}. Custom free-text metrics no longer
+ * progress quests — they no-op at runtime.
  */
 
 /** Metric for purchasing a store offer; auto-reported on purchase. */