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
  • Automated GitHub Releases for non-patch updates, creating a versioned tag and release after merge.
  • Release notes now auto-populated from the CHANGELOG, providing clearer context for each release.
  • Patch updates no longer create tags or releases, reducing noise for end-users.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Renamed the workflow and job, added top-level write permissions, adjusted patch-release log text, and introduced conditional steps to extract release notes from CHANGELOG and create a GitHub Release using softprops/action-gh-release@v2 for non-patch releases, executed after tag creation.

Changes

Cohort / File(s)	Summary of changes
GitHub Actions Workflow .github/workflows/tag-after-merge.yml	Workflow renamed; top-level permissions: write; job renamed; updated patch log message; added non-patch flow to extract notes from CHANGELOG and create a GitHub Release via softprops/action-gh-release@v2 after tagging.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant Dev as Developer
  participant GH as GitHub
  participant WF as Workflow: Tag and Release After Merge
  participant Git as Repo Tags
  participant CL as CHANGELOG.md
  participant Rel as GitHub Releases

  Dev->>GH: Merge to main
  GH->>WF: Trigger workflow
  WF->>WF: Determine release_type (major/minor/patch)
  WF->>Git: Create tag v<version>

  alt release_type == patch
    WF->>GH: Log "Patch release detected → no tag or release will be created."
  else Non-patch (major/minor)
    WF->>CL: Extract notes for <version>
    WF->>WF: Compose env.notes (header + notes)
    WF->>Rel: Create Release (softprops/action-gh-release@v2)<br/>tag: v<version>, name: Release v<version>, body: env.notes
  end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• ci: Add workflow for tagging after merge  #9 — Appears to modify the same workflow by adding release-note extraction and GitHub Release creation, overlapping directly with this PR’s logic.

Poem

A rabbit taps the merge with glee,
Tags hop out: one, two, three—
Patch? We pause and sip our tea;
Minor, Major—notes set free!
A shiny release for all to see,
Changelog crumbs lead happily. 🐇✨

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 bf4ca80 and 07002bf.

📒 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.