docs: Rework npm Publish sections regarding NPM_TOKEN (#108)

* docs: Enhance npm Publish section in WORKFLOWS.md

Updated npm Publish description to include Trusted Publishing.

* Revise required secrets for GitHub release process

Updated the required secrets section for GitHub repository configuration, removing the NPM_TOKEN mention and clarifying the connection to npmjs.com.

* Update .github/WORKFLOWS.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: mfranzke

.github/WORKFLOWS.md

@@ -85,7 +85,7 @@ _Note: Linting has been moved to default.yml to avoid duplication_
 
 - **Test**: Full test suite before release
 - **GitHub Release**: Creates GitHub release with changelog
-- **npm Publish**: Publishes to npm registry (requires `NPM_TOKEN` secret)
+- **npm Publish**: Publishes to npm registry using [Trusted Publishing](https://docs.npmjs.com/trusted-publishers) for secure authentication between GitHub and npmjs.com
 
 ### 5. **Code Quality** (`.github/workflows/quality.yml`)
 

docs/RELEASE_PROCESS.md

@@ -118,9 +118,7 @@ The changeset configuration is in `.changeset/config.json`:
 
 ## Required Secrets
 
-Make sure these secrets are configured in your GitHub repository:
-
-- `NPM_TOKEN`: Your npm authentication token for publishing
+None. The connection in between GitHub pipeline and npmjs.com is done via [Trusted Publishing](https://docs.npmjs.com/trusted-publishers).
 
 ## Benefits over manual tagging
 
@@ -140,7 +138,6 @@ Make sure these secrets are configured in your GitHub repository:
 
 ### Publishing fails
 
-- Verify `NPM_TOKEN` secret is set correctly
 - Check that package name is available on npm
 - Ensure version doesn't already exist