Update release workflow

[scottanderson]

Description:

Update the release workflow.

Please complete the following:

• I have added screenshots for all UI updates
• I process any text displayed to the user through translateText() and I've added it to the en.json file
• I have added relevant tests to the test directory
• I confirm I have thoroughly tested these changes and take full responsibility for any bugs introduced
• I understand that submitting code with bugs that could have been caught through manual testing blocks releases and new features for all contributors

[coderabbitai]

Walkthrough

The release workflow in GitHub Actions was updated to trigger on the "created" and "edited" release events instead of "published." The workflow now also captures and displays the release's name in its output summary, in addition to the tag name and body.

Changes

File(s)	Change Summary
.github/workflows/release.yml	Changed workflow triggers from "published" to "created"; added release name to output summary.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub
    participant Release Workflow

    GitHub->>Release Workflow: Release event ("created" or "edited")
    Release Workflow->>Release Workflow: Extract tag name, body, and release name
    Release Workflow->>Release Workflow: Output summary with tag name, body, and release name

Loading

Possibly related PRs

• Release workflow #1202: Modifies the release workflow trigger events and adds release name to the output, directly related to this PR.

Suggested labels

GitHub Actions

Suggested reviewers

• evanpelle

Poem

When a release is born or changed anew,
The workflow now knows just what to do.
It captures the name, not just the tag,
And prints it out—no need to brag!
A tidy tweak, both clear and bright,
Making summaries just right.
🚀✨

---

📜 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 67754ef and 343f9d1.

📒 Files selected for processing (1)

• .github/workflows/release.yml (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/release.yml

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Deploy to openfront.dev

---

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.
  • Explain this complex logic.
  • 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. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

Documentation and Community

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/release.yml (1)

19-19: Add fallback for missing release name
If github.event.release.name is unset, this will print an empty name. Consider falling back to the tag name to avoid blank output:

RELEASE_NAME: ${{ github.event.release.name || github.event.release.tag_name }}

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b102d1f and 67754ef.

📒 Files selected for processing (1)

• .github/workflows/release.yml (2 hunks)

🔇 Additional comments (2)

.github/workflows/release.yml (2)

6-7: Updated release event triggers
Switching from the published event to created and edited ensures the workflow runs when a release is first drafted and when it’s updated.

---

22-27: Print release info to summary
The step correctly writes the release name, tag, and body into the GitHub Actions summary for easy review.