Skip to content

chore: bump up SnapKit/SnapKit version to from: "5.7.1" #12873

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 20, 2025
Merged

chore: bump up SnapKit/SnapKit version to from: "5.7.1" #12873

merged 1 commit into from
Jun 20, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 20, 2025

This PR contains the following updates:

Package Update Change
SnapKit/SnapKit minor from: "5.0.1" -> from: "5.7.1"

Release Notes

SnapKit/SnapKit (SnapKit/SnapKit)

v5.7.1

Compare Source

  • Podspec bump with privacy manifest support via Cocoapods

v5.7.0

Compare Source

Minor release:

  • Update minimum deployment targets (iOS 12.0, macOS 10.13)
  • Add PrivacyInfo.xcprivacy for Swift PM targets, Cocoapods unsupported due to #​10325

Happy New Year!

v5.6.0

Compare Source

  • Upgrade to syntax compatibility of Swift 5.6
  • Upgrade dependency manager integrations
  • Small tweaks and fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jun 20, 2025
@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 20, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 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? Join our Discord community 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.

@codecov Codecov
Copy link

codecov bot commented Jun 20, 2025 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.05%. Comparing base (eb5a2ff) to head (c266416).
Report is 2 commits behind head on canary.

Additional details and impacted files 
@@            Coverage Diff             @@
##           canary   #12873      +/-   ##
==========================================
- Coverage   56.22%   56.05%   -0.18%     
==========================================
  Files        2658     2658              
  Lines      126968   126982      +14     
  Branches    20109    20029      -80     
==========================================
- Hits        71384    71174     -210     
- Misses      53238    54185     +947     
+ Partials     2346     1623     -723
Flag Coverage Δ
server-test 78.88% <ø> (-0.89%) ⬇️
unittest 31.76% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@fengmk2 fengmk2 requested a review from Lakr233 June 20, 2025 06:23
@fengmk2 fengmk2 enabled auto-merge June 20, 2025 06:23
@fengmk2 fengmk2 requested a review from Copilot June 20, 2025 06:23
Copilot
Copilot AI reviewed Jun 20, 2025
View reviewed changes
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

Update the SnapKit Swift Package dependency from version 5.0.1 to 5.7.1 to incorporate the latest privacy manifest support and deployment target updates.

  • Bumps .package reference for SnapKit to from: "5.7.1".

@fengmk2 fengmk2 added this pull request to the merge queue Jun 20, 2025
Merged via the queue into canary with commit fb250c6 Jun 20, 2025
111 checks passed
@fengmk2 fengmk2 deleted the renovate/snapkit-snapkit-5.x branch June 20, 2025 07:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

Copilot code review Copilot Copilot left review comments

@Lakr233 Lakr233 Lakr233 approved these changes

Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
AFFiNE Project
Status: No status
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@Lakr233 @fengmk2