ci(release): auto-publish on package.json version change

[simaonogueira101]

Summary

Removes the manual git tag && git push --tags step from releasing. The workflow now:

• Triggers on push to main only when package.json is touched.
• Detects whether version actually changed vs HEAD~1. If unchanged → skip everything.
• Refuses to re-publish if v<version> already exists on the remote.
• Runs lint + check-types + tests + build before publish (same gates as before).
• Publishes to npm with provenance.
• Creates + pushes the v<version> git tag from the workflow itself, so git history still marks every release.
• workflow_dispatch with force=true lets you force-publish at the current version (useful for re-releasing after a failed publish without bumping).

Why

Until now the release flow required an extra manual step after merging a version-bump PR:

git checkout main && git pull
git tag v0.3.0 && git push origin v0.3.0

That step is easy to forget and adds friction. The new flow makes the version bump in package.json the single source of release intent: bump it in your feature PR, merge, done.

Safety properties preserved

• Only intentional version bumps publish — a feature PR that doesn't touch package.json is a no-op for the workflow.
• The same lint / types / test / build gates run before npm publish.
• Provenance is still enabled.
• The "tag already exists" check prevents accidental re-publish of an already-shipped version.

Test plan

• YAML parsed and committed (CI will compile-check on next push).
• Merge this PR — workflow should NOT fire (this PR changes release.yml, not package.json).
• First real test: next feature PR that bumps version → workflow publishes + tags automatically.

🤖 Generated with Claude Code