Skip to content

Conversation

@chirag127
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade expo-linking from 7.0.5 to 7.1.7.

ℹ️ 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.


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

  • The recommended version was released 5 months ago.

Release notes
Package name: expo-linking
  • 7.1.7 - 2025-07-03
  • 7.1.7-canary-20250701-6a945c5 - 2025-07-01
  • 7.1.6 - 2025-07-01
  • 7.1.6-canary-20250630-547cd82 - 2025-06-30
  • 7.1.6-canary-20250613-b29d676 - 2025-06-13
  • 7.1.6-canary-20250612-338ef55 - 2025-06-12
  • 7.1.6-canary-20250611-f0afe80 - 2025-06-11
  • 7.1.5 - 2025-05-08
  • 7.1.4 - 2025-04-30
  • 7.1.3 - 2025-04-25
  • 7.1.2 - 2025-04-14
  • 7.1.1 - 2025-04-09
  • 7.1.1-canary-20250408-7f0ab53 - 2025-04-08
  • 7.1.1-canary-20250407-10a9b42 - 2025-04-07
  • 7.1.0 - 2025-04-04
  • 7.1.0-canary-20250404-87e2506 - 2025-04-04
  • 7.1.0-canary-20250404-42b6263 - 2025-04-04
  • 7.1.0-canary-20250404-3c3b5fd - 2025-04-04
  • 7.1.0-canary-20250403-13261ac - 2025-04-02
  • 7.1.0-canary-20250402-161f57b - 2025-04-02
  • 7.1.0-canary-20250331-817737a - 2025-03-31
  • 7.1.0-canary-20250320-7a205d3 - 2025-03-20
  • 7.1.0-canary-20250306-d9d3e02 - 2025-03-06
  • 7.1.0-canary-20250305-0af9ad2 - 2025-03-05
  • 7.1.0-canary-20250304-f08e984 - 2025-03-04
  • 7.1.0-canary-20250304-8a21aa7 - 2025-03-04
  • 7.1.0-canary-20250304-0da3971 - 2025-03-04
  • 7.1.0-canary-20250303-4dba60e - 2025-03-03
  • 7.1.0-canary-20250221-ef26fed - 2025-02-21
  • 7.1.0-canary-20250219-4a5dade - 2025-02-19
  • 7.1.0-canary-20250207-8bc5146 - 2025-02-07
  • 7.1.0-canary-20250131-5c4e588 - 2025-01-31
  • 7.1.0-canary-20250124-42fe332 - 2025-01-24
  • 7.0.5 - 2025-01-27
from expo-linking GitHub release notes

Important

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

Snyk has created this PR to upgrade expo-linking from 7.0.5 to 7.1.7.

See this package in npm:
expo-linking

See this project in Snyk:
https://app.snyk.io/org/whyiswhen/project/9c3706d7-229d-4aa3-819f-c3a61957030a?utm_source=github&utm_medium=referral&page=upgrade-pr
@continue
Copy link

continue bot commented Dec 4, 2025

Keep this PR in a mergeable state →

Learn more

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

@coderabbitai
Copy link

coderabbitai bot commented Dec 4, 2025

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. 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.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch snyk-upgrade-4570d11ca0f6df80d2bafdd250d48f86

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist
Copy link

Summary of Changes

Hello @chirag127, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, updates the expo-linking package to its latest stable version, 7.1.7. This upgrade aims to keep project dependencies current, enhancing security and maintainability by incorporating the latest fixes and features from the expo-linking module and its newly introduced sub-dependencies.

Highlights

  • Dependency Upgrade: The expo-linking package has been upgraded from version 7.0.5 to 7.1.7.
  • Transitive Dependencies: This upgrade introduces several new transitive dependencies for expo-linking, including various @expo configuration and utility packages, @babel/code-frame, getenv, semver, and XML/plist parsing libraries.
  • Package Lock File Adjustment: The expo dependency in package-lock.json has been adjusted from ^52.0.47 to ~52.0.47.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@socket-security
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedexpo-linking@​7.0.5 ⏵ 7.1.710010080 +1100100

View full report

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request, automatically generated by Snyk, upgrades the expo-linking dependency from version 7.0.5 to 7.1.7. While updating dependencies is a good practice, I've identified a critical inconsistency between package.json and package-lock.json for the expo-linking version constraint. I have provided a suggestion to resolve this, which will ensure dependency resolution remains predictable and stable.

"expo-font": "~13.0.4",
"expo-haptics": "~14.0.1",
"expo-linking": "~7.0.5",
"expo-linking": "~7.1.7",

Choose a reason for hiding this comment

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

critical

There is an inconsistency between package.json and package-lock.json for the expo-linking dependency. package.json specifies ~7.1.7, while package-lock.json specifies ^7.1.7. This can lead to issues with dependency resolution and unpredictable builds.

To ensure consistency and follow best practices for allowing non-breaking updates, it's recommended to use the caret (^) operator in package.json to match the package-lock.json.

Suggested change
"expo-linking": "~7.1.7",
"expo-linking": "^7.1.7",

@chirag127 chirag127 merged commit 44c9593 into master Dec 6, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants