ci: add major/minor release heading in GitHub release notes

[taj54]

• Updated release notes extraction to prepend heading based on release type
  • 🚀 Major Release
  • ✨ Minor Release
• Ensures GitHub release body includes contextual heading + changelog content

Summary by CodeRabbit

• Chores
  • Updated automation to publish GitHub Releases for major/minor merges, alongside tags.
  • Release notes are auto-extracted from the CHANGELOG and included in each release.
  • Patch-only changes will no longer create tags or releases.
  • Adjusted workflow permissions to enable release publishing.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The GitHub Actions workflow .github/workflows/tag-after-merge.yml was updated to both tag and create a GitHub Release after merges. It adds write permissions, renames the job, updates messages, extracts release notes from CHANGELOG for major/minor releases, and publishes a release using softprops/action-gh-release.

Changes

Cohort / File(s)	Summary
GitHub Actions: Tag + Release workflow .github/workflows/tag-after-merge.yml	Renamed workflow and job; added contents: write permissions; refined patch message; added steps to extract release notes from CHANGELOG for major/minor releases; created GitHub Release via softprops/action-gh-release using v tag and assembled notes; no tag/release for patch.

Sequence Diagram(s)

sequenceDiagram
    actor Dev as Developer
    participant GH as GitHub
    participant WF as Workflow: tag-and-release
    participant Repo as Repo/CHANGELOG
    participant GHRel as GitHub Releases

    Dev->>GH: Merge to default branch
    GH->>WF: Trigger workflow
    WF->>Repo: Checkout
    WF->>Repo: Get last tag / compute next version
    alt Patch release
        WF-->>GH: Log "no tag or release"
        WF-->>WF: Exit job
    else Major/Minor release
        WF->>Repo: Create tag v<version>
        WF->>Repo: Extract release notes (CHANGELOG section)
        WF->>WF: Build notes env (header + contents)
        WF->>GHRel: Create Release for v<version> (softprops/action-gh-release)
        GHRel-->>WF: Release published
    end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• feat: Add tag-after-merge workflow #26 — Also modifies .github/workflows/tag-after-merge.yml, extending tagging logic; closely aligned with adding release creation.

Poem

A whisk of tags, a hop of release,
I nudge the changelog—notes on a breeze.
Major? Minor? I thump with cheer,
Patch gets a wink: “No fireworks here.”
Carrot-shaped confetti in versioned light—
v-bundles launched into the night! 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 24f24a9 and 171a6b9.

📒 Files selected for processing (1)

• .github/workflows/tag-after-merge.yml (3 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.