Remove npm token from publish workflow (#2)

* Remove npm token from publish workflow

Use npm trusted publishing instead of token-based authentication.
The workflow already has id-token: write permission and --provenance
flag which enables OIDC-based trusted publishing.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

* Set version to 0.0.0 and use release tag for npm publish

The package.json version is now set to 0.0.0 in the repository. The publish workflow extracts the version from the GitHub release tag and applies it before publishing to npm.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

---------

Co-authored-by: Claude <[email protected]>

Author: MrTravisB

.github/workflows/publish.yml

@@ -62,7 +62,12 @@ jobs:
           ls -la dist/esm/
           ls -la dist/types/
 
+      - name: Set version from release tag
+        run: |
+          # Extract version from release tag (e.g., v1.2.3 -> 1.2.3)
+          VERSION=${GITHUB_REF#refs/tags/v}
+          echo "Setting version to $VERSION"
+          npm version $VERSION --no-git-tag-version
+
       - name: Publish to npm
         run: npm publish --provenance --access public
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tabstack/sdk",
-  "version": "1.0.0",
+  "version": "0.0.0",
   "description": "TypeScript/JavaScript SDK for TABStack AI - Extract, Generate, and Automate web content",
   "main": "./dist/cjs/index.js",
   "module": "./dist/esm/index.js",