Template update

[NSFatalError]

Summary by CodeRabbit

• Chores
  • Refined the release versioning process to improve the accuracy of determining previous release versions.
  • Enhanced version sorting output to support better management of the release history.
  • Updated workflow to run on macOS and added support for Xcode versioning.

[coderabbitai]

Walkthrough

The pull request modifies the release workflow in the GitHub Actions configuration. Key changes include the addition of the XCODE_VERSION environment variable set to "16.3", a switch from ubuntu-latest to macos-15, and an update to the checkout step with fetch-depth: 0. A new step for setting up Xcode has been introduced, and adjustments have been made to the API-breaking changes verification logic to allow the workflow to continue despite potential errors. The draft release step has been repositioned to the end of the job.

Changes

File	Change Summary
.github/workflows/release.yml	Added XCODE_VERSION variable; changed OS to macos-15; updated checkout to fetch-depth: 0; added Xcode setup step; modified API-breaking changes command for error handling; moved draft release step to the end.

Possibly related PRs

• Template update #6: The changes in the main PR and the retrieved PR are related as both involve modifications to GitHub Actions workflow files, specifically addressing the handling of versioning and error management in the context of Xcode, although they focus on different aspects of the workflows.

Poem

I'm a rabbit, hopping with glee,
Xcode's set up, as fine as can be!
From Ubuntu to Mac, we leap and we bound,
New workflows in place, with joy all around!
Hopping through code, our spirits unbound.
🥕🐇

---

📜 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 0ce5eab and c3c6459.

📒 Files selected for processing (1)

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

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

• .github/workflows/release.yml

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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 (2)

.github/workflows/release.yml (2)

26-26: Update to Previous Tag Retrieval Logic

The command now retrieves the third most recent tag using head -n 3 | tail -n 1 instead of the previous mechanism. Please verify that this behavior accurately reflects the intended versioning strategy and that there will always be at least three tags to avoid unexpected empty values.

---

30-30: Diagnostic Tag Listing Output

The addition of echo $(git tag --sort=-v:refname) helps by outputting the sorted list of tags, which is useful for debugging. Consider quoting the command substitution (e.g., echo "$(git tag --sort=-v:refname)") to safeguard against potential issues with tags that contain spaces.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1b094de and a0b5833.

📒 Files selected for processing (1)

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/release.yml (1)

25-27: Ensure Repository Tags Are Up-to-Date & Remove Trailing Whitespaces

The newly added commands:

• git fetch --tags ensures that the local repository is updated with the latest tags.
• echo $(git tag --sort=-v:refname) prints the sorted list of tags for verification.

Please remove the trailing spaces on line 27 to adhere to YAML formatting best practices.

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 27-27: trailing spaces

(trailing-spaces)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a57ea07 and 0ce5eab.

📒 Files selected for processing (1)

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

🧰 Additional context used

🪛 YAMLlint (1.35.1)

.github/workflows/release.yml

[error] 27-27: trailing spaces

(trailing-spaces)

🔇 Additional comments (1)

.github/workflows/release.yml (1)

28-29: Confirm Updated Tag Selection Logic

The previous tag is now determined using:

previous_tag=$(git tag --sort=-v:refname | head -n 3 | tail -n 1)

This change picks the third most recent tag, aligning with the PR objectives for the release workflow. Please verify that this new behavior matches your intended version flow.