ci: Drop support for macOS 13 & 14 mirroring y-scope/clp#1130.

[davidlion]

Description

This PR drops macos-13 and macos-14 from CI as they are no longer required by CLP since y-scope/clp#1130. Similar to that PR, this also prepares log-surgeon for the eventual addition of ystdlib-cpp.

We also drop brew install coreutils as it is unnecessary in macos-15.

Checklist

• The PR satisfies the contribution guidelines.
• This is a breaking change and that has been indicated in the PR title, OR this isn't a
  breaking change.
• Necessary docs have been updated, OR no docs need to be updated.

Validation performed

CI passing.

Summary by CodeRabbit

• Chores
  • Updated build workflow to only run on macOS 15 and Ubuntu 22.04/24.04, removing older macOS versions.
  • Removed the step that installed coreutils on macOS 15 runners in the lint workflow.

[coderabbitai]

Walkthrough

The GitHub Actions workflow configurations were updated. The build workflow now only runs on macOS 15 and Ubuntu 22.04/24.04, dropping support for macOS 13 and 14. In the lint workflow, the step installing coreutils on macOS 15 was removed; all other steps remain unchanged.

Changes

Cohort / File(s)	Change Summary
Build Workflow OS Matrix Update .github/workflows/build.yaml	Removed "macos-13" and "macos-14" from the build matrix; only "macos-15", "ubuntu-22.04", and "ubuntu-24.04" remain.
Lint Workflow macOS Step Removal .github/workflows/lint.yml	Deleted the conditional step that installed coreutils on "macos-15" runners.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix(gh-workflow): Lock Ubuntu runner to 22.04 as a temporary workaround for #75. #80: Both PRs modify the OS matrix in the GitHub Actions build workflow to specify supported operating system versions, focusing on controlling which OS versions are used for builds.

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3c41d51 and f2eb42f.

📒 Files selected for processing (2)

• .github/workflows/build.yaml (0 hunks)
• .github/workflows/lint.yml (0 hunks)

💤 Files with no reviewable changes (2)

• .github/workflows/build.yaml
• .github/workflows/lint.yml

✨ 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.
  • 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 docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for 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.

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.

[SharafMohamed]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.