fix: release workflow semver-aware bumps and branch protection

[GeiserX]

Summary

• Detect feat:/BREAKING commits for minor/major version bumps (was always patch)
• Remove package.json push to main (blocked by branch protection rules)
• Create tag after package.json sync to keep them consistent (CodeRabbit suggestion)
• Bump package.json to 0.3.0 for multi-broker feature release

Summary by CodeRabbit

• Chores

  • Updated release automation to detect version bump type from commit messages (minor for features, major for breaking changes, patch otherwise).
  • Optimized release workflow sequencing for improved package version synchronization.

• Version

  • Bumped version to 0.3.0.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

The release workflow now determines version bumps based on commit message patterns (feat → minor, BREAKING → major, otherwise patch) instead of unconditionally incrementing patch. Tag creation was reordered after package synchronization. Package version was bumped to 0.3.0.

Changes

Cohort / File(s)	Summary
Release Workflow .github/workflows/release.yml	Modified version-bump detection to parse commit messages for semantic version increments (minor for feat(), major for BREAKING). Reordered tag-creation step and removed file commits from package-sync step.
Package Manifest package.json	Version updated from 0.2.0 to 0.3.0.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 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 changes: semver-aware version bumping (feat/breaking detection) and branch protection compliance in the release workflow.
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/release-workflow

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.78%. Comparing base (5f3a2ca) to head (0302362).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #13   +/-   ##
=======================================
  Coverage   65.78%   65.78%           
=======================================
  Files          20       20           
  Lines        1438     1438           
  Branches      284      284           
=======================================
  Hits          946      946           
  Misses        491      491           
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.