Skip to content

[Snyk] Upgrade sonner from 1.7.0 to 2.0.2 #111

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
Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

[Snyk] Upgrade sonner from 1.7.0 to 2.0.2 #111

wants to merge 1 commit into from

Conversation

nerdy-tech-com-gitub
Copy link
Owner

@nerdy-tech-com-gitub nerdy-tech-com-gitub commented Apr 20, 2025 •
edited by sourcery-ai bot
Loading

Sweep Summary Sweep

Implements a new "Follow" feature allowing users to follow other users through the Android app's main activity.

  • Added a new FollowResponse data class in data/model/FollowResponse.kt to handle API responses for follow actions.
  • Created a new follow endpoint in UserService.kt and implemented the follow functionality in UserRepository.kt and UserRepositoryImpl.kt.
  • Enhanced MainViewModel.kt with methods to handle follow actions and update UI state accordingly.
  • Updated MainActivity.kt with a click handler for the follow button and UI state management.
  • Added a Follow button to the main activity layout in activity_main.xml.

Ask Sweep AI questions about this PR

snyk-top-banner

Snyk has created this PR to upgrade sonner from 1.7.0 to 2.0.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

  • The recommended version is 11 versions ahead of your current version.

  • The recommended version was released 24 days ago.

Release notes
Package name: sonner from sonner GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Summary by Sourcery

Enhancements:

  • Upgrade to the latest major version of sonner, which includes several improvements and bug fixes

@snyk-bot
feat: upgrade sonner from 1.7.0 to 2.0.2
604cd66 
Snyk has created this PR to upgrade sonner from 1.7.0 to 2.0.2.

See this package in npm:
sonner

See this project in Snyk:
https://app.snyk.io/org/nerds-github/project/f46aeb9c-67b0-476f-be8c-803dad4ffe08?utm_source=github&utm_medium=referral&page=upgrade-pr
@sourcery-ai Sourcery AI
Copy link

sourcery-ai bot commented Apr 20, 2025 •
edited
Loading

Reviewer's Guide by Sourcery

This pull request upgrades the sonner dependency from version 1.7.0 to 2.0.2 by modifying the version number in package.json.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
The pull request upgrades the sonner dependency from version 1.7.0 to 2.0.2.
  • Updated the sonner version in package.json.
 packages/shared/package.json
Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

sourcery-ai[bot]
sourcery-ai bot reviewed Apr 20, 2025
View reviewed changes
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sourcery-ai sourcery-ai[bot] sourcery-ai[bot] left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@nerdy-tech-com-gitub @snyk-bot