From ff0a05d991ee6a2d203cabfaaf7cd9c134cbbbda Mon Sep 17 00:00:00 2001
From: Kuba Adamczyk <jakub.adamczyk@phantom.app>
Date: Mon, 26 Jan 2026 13:25:29 +0100
Subject: [PATCH] do not use changesets to do the publish, publish manually
 instead

---
 .github/workflows/release.yml | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index d0e6e14ab..c416c425d 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -40,16 +40,15 @@ jobs:
       - name: Install Dependencies
         run: yarn
 
-      - name: Create Release Pull Request or Publish to npm
+      - name: Create Release Pull Request
         id: changesets
         uses: changesets/action@e0145edc7d9d8679003495b11f87bd8ef63c0cba
         with:
-          # This expects you to have a script called release which does a build for your packages and calls changeset publish
           version: yarn changeset version
-          publish: yarn release
           commitMode: github-api
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          # we use trusted publishing and setup-node will set these incorrectly. Unset if we ever use RO_TOKEN
-          NODE_AUTH_TOKEN: ""
-          NPM_CONFIG_PROVENANCE: true
+
+      - name: Publish to npm (OIDC Trusted Publishing)
+        if: steps.changesets.outputs.hasChangesets == 'false'
+        run: yarn release