Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI Update: Use macOS 14 runner #29

Merged
merged 2 commits into from
Mar 6, 2024
Merged

Conversation

phil1995
Copy link
Collaborator

@phil1995 phil1995 commented Mar 5, 2024

On January 30, 2024, Github introduced the macOS Sonoma image and made it possible to use M1 macOS Runner.

As before the runner is available for free in public repositories:

This runner is available for all plans, free in public repositories, and eligible to consume included free plan minutes in private repositories.

In addition I've did minor upgrades to the used actions:

  • bumped actions/checkout to v4
  • bumped actions/cache to v4

Explicitly set the used Xcode version to 15.2.

The only downside is that the new arm64 based image does not have SwiftLint pre-installed therefore I've added an additional step.

Basically the same as with: cryptomator/ios#339

The only difference is that I needed to fix a SwiftFormat linter warning because otherwise the CI would not pass.

Summary by CodeRabbit

  • Chores

    • Updated the macOS version to 14 for build and release processes.
    • Updated GitHub actions for checkout and cache to version 4.
    • Added SwiftLint installation and configured Xcode 15.2 for the build environment.
  • New Features

    • Enhanced Dropbox integration in the app.

@phil1995 phil1995 requested a review from tobihagemann March 5, 2024 20:38
Copy link

coderabbitai bot commented Mar 5, 2024

Walkthrough

The recent updates focus on enhancing the development environment and codebase for a project. The changes include upgrading the macOS version and Xcode in the CI/CD pipeline, updating essential GitHub Actions, incorporating SwiftLint for code quality checks, and refining the build and test commands. Additionally, the codebase is improved by ensuring the necessary import of Foundation in a specific Dropbox setup file, promoting better structure and functionality within the project.

Changes

File Path Change Summary
.github/workflows/build.yml Upgraded macOS to 14, updated GitHub Actions, added SwiftLint, selected Xcode 15.2, adjusted build/test commands
Sources/.../Dropbox/DropboxSetup.swift Added Foundation import

🐰✨
In the land of code and byte,
Where the bits dance day and night,
A rabbit hopped with glee and might,
For the project shines, oh so bright.
Upgrades here and imports there,
A swift move, beyond compare.
🌟🚀

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

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>.
    • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 248e6e6 and d1f5751.
Files selected for processing (2)
  • .github/workflows/build.yml (2 hunks)
  • Sources/CryptomatorCloudAccess/Dropbox/DropboxSetup.swift (1 hunks)
Additional comments: 6
Sources/CryptomatorCloudAccess/Dropbox/DropboxSetup.swift (1)
  • 7-7: The addition of import Foundation is standard practice in Swift development for accessing fundamental data types and functionalities, especially in a context like DropboxSetup that likely involves networking and data handling.
.github/workflows/build.yml (5)
  • 9-9: Updating the runner to macos-14 aligns with the PR's objective to leverage the latest macOS version and the M1 macOS Runner's capabilities. This should enhance the CI process by utilizing the latest hardware and software advancements.
  • 15-16: Upgrading actions/checkout and actions/cache to version 4 ensures the workflow benefits from the latest features and improvements in these actions. It's important to keep these actions up-to-date for efficiency and security reasons.
  • 22-23: The addition of SwiftLint installation via brew install swiftlint addresses the absence of SwiftLint in the macOS Sonoma image. This step ensures that linting checks continue to be part of the CI process, which is crucial for maintaining code quality and style consistency.
  • 28-29: Explicitly setting the Xcode version to 15.2 with sudo xcode-select -s /Applications/Xcode_15.2.app ensures consistency and compatibility with the project's requirements. This step is essential for a reliable CI process, as it guarantees the use of the correct Xcode version.
  • 28-29: Adjustments to the Xcode build and test commands, as well as the update to macos-14 for the release job, are correctly implemented to align with the new CI environment setup. These changes are necessary for leveraging the latest macOS and Xcode versions, ensuring the CI process is optimized for performance and compatibility.

Also applies to: 66-66

Copy link
Member

@tobihagemann tobihagemann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! 🚀

@tobihagemann tobihagemann merged commit 2fa650a into develop Mar 6, 2024
3 checks passed
@tobihagemann tobihagemann deleted the feature/update-ci-macos-14 branch March 6, 2024 07:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants