Restore auto version bump in publish workflow

[joalves]

Adds back the conventional-commit version bump that was accidentally removed. Bumps patch/minor/major based on commit messages since last tag, then publishes and pushes the version commit + tag back to main.

Summary by CodeRabbit

• Chores
  • Enhanced the automated release workflow with intelligent semantic versioning. The updated pipeline now analyses commit messages to automatically determine appropriate version increments, manages package version updates comprehensively, creates and manages version tags properly, publishes packages, and synchronises all changes back to the repository for more reliable and consistent releases.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

Walkthrough

The pull request modifies the .github/workflows/publish.yml workflow file to implement automated semantic versioning and publishing. The job permissions are expanded from contents: read to contents: write. The checkout action now retrieves full history with fetch-depth: 0 to enable version delta computation. New workflow steps inspect commit messages for semantic version bump indicators, execute npm version to update package.json, create an explicit git commit and v{VERSION} tag, publish the package via npm publish, and push the commit and tags to the remote repository using git push --follow-tags. The control flow is restructured so version mutation and tagging occur before the build/publish sequence, with the final push happening after publishing completes.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• Auto-bump version from conventional commits #5: Implements the identical code-level changes to .github/workflows/publish.yml, including full-history checkout, permission expansion, semantic version detection, and npm version bump logic.
• Match working publish config from absmartly-cli-ts #14: Modifies the same workflow file and alters job permissions (contents and id-token), directly overlapping with permission-related changes.
• Use release-please for versioning and npm trusted publishing #7: Modifies the repository's publishing workflow and version-bump/publish steps, providing alternative approaches to release automation.

Poem

🐰 Through commit messages the rabbit peers,
Bumps the version with npm cheers,
Tags and commits with git-fu grace,
Pushes to the repo at blazing pace,
Publish flows—now fully automated! 🎉

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main objective: restoring automatic version bumping functionality to the publish workflow, which is directly supported by the changeset that adds version detection and bumping logic.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/restore-version-bump

---

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