Skip to content

[Snyk] Security upgrade appium from 1.18.3 to 2.0.0 #434

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mCodex
Copy link
Owner

@mCodex mCodex commented Jun 6, 2025

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • example/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Improper Link Resolution Before File Access ('Link Following')
SNYK-JS-TARFS-10293725
  721  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • 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 fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Improper Link Resolution Before File Access ('Link Following')

@Copilot Copilot AI review requested due to automatic review settings June 6, 2025 05:39
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

This PR updates the example project's Appium dependency to fix a high-severity vulnerability identified by Snyk.

  • Bump Appium from ^1.18.3 to ^2.0.0 in example/package.json
  • Reminder to regenerate the lockfile to reflect the version change
Comments suppressed due to low confidence (1)

example/package.json:19

  • Confirm that Appium v2.0.0 is backward-compatible with the example’s existing scripts/configuration and update any deprecated options or command flags as needed.
"appium": "^2.0.0",

@@ -16,7 +16,7 @@
"@react-native-community/masked-view": "^0.1.10",
"@react-navigation/native": "^5.7.2",
"@react-navigation/stack": "^5.8.0",
"appium": "^1.18.3",
"appium": "^2.0.0",
Copy link
Preview

Copilot AI Jun 6, 2025

Choose a reason for hiding this comment

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

After bumping the Appium version, regenerate the yarn.lock (e.g., run yarn install) to keep the lockfile in sync and prevent version mismatches.

Copilot uses AI. Check for mistakes.

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