Update dependencies

[phil1995]

Updates the dependencies:

Dropbox from 7.0.0 to 7.2.0
CocoaLumberjack from 3.8.1 to 3.8.5
MSAL from 1.2.16 to 1.3.0
AWS SDK from 2.33.4 to 2.34.0
Google APIs Client Library from 3.2.0 to 3.5.1

Summary by CodeRabbit

• Chores
  • Updated minimum versions for various Swift packages to ensure compatibility and security.
  • Updated remote source control locations and versions for dependencies such as AWS SDK, Dropbox SDK, Google API, and Microsoft Authentication Library to enhance functionality and stability.

[coderabbitai]

Walkthrough

The updates involve raising the minimum versions for a variety of Swift packages, focusing on dependencies used for cloud services and authentication, including the Google API, Dropbox SDK, AWS SDK, and Microsoft Authentication Library. These changes reflect a broader move to ensure compatibility and security by leveraging the latest versions of these critical libraries.

Changes

File Path	Change Summary
CryptomatorCloudAccess.../project.pbxproj	Updated minimum versions for Swift packages such as google-api-objectivec-client-for-rest, dropbox-sdk-obj-c-spm, etc.
CryptomatorCloudAccess.../project.xcworkspace/.../Package.resolved	Updated remote source control locations, revisions, and versions for dependencies like AWS SDK, Dropbox SDK, etc.
Package.resolved	Updated revision and version numbers for dependencies including aws-sdk-ios, CocoaLumberjack, etc.
Package.swift	Updated dependency versions for libraries like Microsoft Authentication Library for Objective-C, AWS SDK for iOS, etc.

🐰✨
In the realm of code, where the swift packages dwell,
A rabbit hopped through, casting an update spell.
"Rise, dear versions, to heights anew,
For security and compatibility, through and through."
With a flick and a hop, the deed was done,
In the land of the cloud, a new day begun.
🌟📦🔒

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

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

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 2fa650a and 35927b4.

Files selected for processing (4)

• CryptomatorCloudAccess.xcodeproj/project.pbxproj (4 hunks)
• CryptomatorCloudAccess.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved (3 hunks)
• Package.resolved (5 hunks)
• Package.swift (1 hunks)

Additional comments: 14

Package.swift (4)

• 31-31: The dependency for the Microsoft Authentication Library for Objective-C has been updated to version 1.3.0. This update is aligned with the PR objectives and should introduce new authentication features or security patches. Ensure that the project's authentication flows are tested thoroughly to verify compatibility with the new library version.
• 32-32: The AWS SDK for iOS has been updated to version 2.34.0. Given the critical role of AWS services in many projects, it's important to review any changes in the SDK's documentation for breaking changes or deprecations that could affect the project. Additionally, testing the integration with AWS services is recommended to ensure that the update does not introduce any regressions.
• 35-35: The Google API Objective-C client for REST has been updated to version 3.5.0. This is a significant version jump, which could include new functionalities or bug fixes. It's crucial to verify that the project's interactions with Google APIs remain functional and to explore new features that could benefit the project.
• 42-42: The Dropbox SDK for Objective-C has been updated to version 7.2.0. This update is expected to enhance cloud storage integration capabilities. Testing the Dropbox integration thoroughly is recommended to ensure that file operations (upload, download, list, etc.) work as expected with the new SDK version.

CryptomatorCloudAccess.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved (4)

• 17-18: The resolved version for the AWS SDK (2.34.0) matches the update specified in Package.swift. This consistency is crucial for ensuring that the project uses the intended versions of its dependencies. No action is required, but it's good practice to verify that the integration with AWS services functions as expected after the update.
• 53-54: The resolved version for the Dropbox SDK (7.2.0) is consistent with the update in Package.swift. As Dropbox plays a significant role in cloud storage integration, ensure that all Dropbox-related functionalities are tested to confirm compatibility with the new SDK version.
• 62-63: The resolved version for the Google API Objective-C client for REST (3.5.1) correctly reflects the update intended in Package.swift. Given the importance of Google API interactions, it's recommended to test these integrations thoroughly to ensure that the update does not introduce any issues.
• 107-108: The resolved version for the Microsoft Authentication Library for Objective-C (1.3.0) matches the update in Package.swift. It's important to test authentication flows within the project to verify that they work as expected with the new version of the library.

Package.resolved (6)

• 17-18: The resolved version for the AWS SDK (2.34.0) in this file is consistent with the updates made in Package.swift. This consistency across different package resolution files is important for maintaining the integrity of dependency management. Ensure that AWS service integrations are functioning as expected after the update.
• 35-36: The resolved version for CocoaLumberjack (3.8.5) reflects the intended update, enhancing logging efficiency and reliability. It's advisable to check the logging output to ensure that the update has not affected the logging functionality negatively.
• 53-54: The resolved version for the Dropbox SDK (7.2.0) matches the intended update in Package.swift. As with the previous file, confirm that Dropbox integration tests pass to ensure compatibility with the new SDK version.
• 62-63: The resolved version for the Google API Objective-C client for REST (3.5.1) is correctly updated. Testing Google API interactions is recommended to verify that the project benefits from the new functionalities or bug fixes introduced in this version.
• 107-108: The resolved version for the Microsoft Authentication Library for Objective-C (1.3.0) is consistent with the update specified in Package.swift. Testing authentication flows is crucial to ensure that the update does not introduce any regressions.
• 150-153: The swift-log package has been updated to version 1.5.4. This update is not explicitly mentioned in the PR objectives or the AI-generated summary but is an important part of maintaining up-to-date dependencies. Ensure that the logging functionality throughout the project remains unaffected by this update.