Fix publishing from a fork

[kibertoad]

Summary by CodeRabbit

• Chores
  • Updated release workflow to automatically publish on main branch commits
  • Enhanced release process with improved reliability, serialization, and duplicate-prevention safeguards
  • Streamlined multi-package release handling and reporting

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

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The CI/CD release workflow transitions from pull-request-triggered publishing to main-branch push events, consolidates multi-job orchestration into a single streamlined release job, and implements dynamic package matrix computation with PR-label-based version bumping and idempotent publishing checks.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Restructuring .github/workflows/publish.yml	Refactored trigger logic from pull_request closed events to push on main branch; introduced workflow-wide concurrency serialization; redesigned detect-changes job with PR info extraction, PR-label-derived version bump determination (patch, minor, major), and dynamic multi-package matrix computation; consolidated separate publish/tag jobs into single release job with integrated install, version-bump, build, and multi-package publish loop; added skip-check for version-bump commits; implemented idempotency check before package publishing; unified tag creation and push operations.
Documentation Formatting packages/kafka/README.md	Introduced whitespace-only line after header; no functional changes.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~60 minutes

Areas requiring extra attention:

• PR info extraction logic and the gh api integration for label-based version-bump detection
• Dynamic matrix builder logic that filters changed packages and constructs the multi-package build matrix
• Consolidation of the release job and the sequencing of bump → build → publish → tag operations
• Idempotency check logic before publishing to prevent duplicate releases
• Interactions between conditional outputs (has_changes, should_publish, bump) and downstream job logic

Poem

🐰 Hops with glee through main branch gates,
No more PR waits—releases actuate!
One job to rule them all with grace,
Dynamic matrices, labels in place,
Idempotent publishes, bunny's release embrace!
✨📦

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/fork-publish

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6210dad and 9f048c6.

📒 Files selected for processing (2)

• .github/workflows/publish.yml (4 hunks)
• packages/kafka/README.md (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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