do not use changesets to do the publish, publish manually instead

[jkadamczyk]

Summary by CodeRabbit

• Chores
  • Updated the release and publishing workflow to separate Release PR creation from npm publishing, implementing OIDC Trusted Publishing for enhanced security and reliability.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

GitHub Actions release workflow refactored to decouple Release PR creation from npm publishing. The publish step now runs separately as a conditional step using OIDC Trusted Publishing when changesets are absent.

Changes

Cohort / File(s)

Summary

Release Workflow Refactoring .github/workflows/release.yml

Split combined Release PR/publish step into two separate steps: (1) Create Release Pull Request step simplified to remove direct publish invocation and environment variable configuration, (2) New Publish to npm step added with OIDC Trusted Publishing, conditioned on steps.changesets.outputs.hasChangesets == 'false'. Removed NODE_AUTH_TOKEN and NPM_CONFIG_PROVENANCE environment variables from Release PR step.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}