[Snyk] Fix for 1 vulnerabilities

[mCodex]

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
	Symlink Attack SNYK-JS-TMP-11501554	733

---

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[Copilot]

Pull Request Overview

This PR fixes a Snyk-identified security vulnerability (SNYK-JS-TMP-11501554) by upgrading multiple dependencies in the example package. The vulnerability has a medium severity score of 733 and involves a symlink attack in the tmp package.

• Updates four key dependencies to their latest stable versions
• Addresses a symlink attack vulnerability in the dependency chain
• Represents breaking changes that may require additional testing

[Copilot]

The upgrade from appium 1.18.3 to 2.0.0 is a major version change that introduces breaking changes. This requires updating test scripts and potentially changing the API usage patterns. Ensure all appium-related code is compatible with v2.0.0 before merging.

Suggested change

	"appium": "^2.0.0",
	"appium": "1.18.3",

[Copilot]

The upgrade from React Native 0.63.2 to 0.69.12 spans multiple major versions and includes significant breaking changes. This upgrade requires updating native code, build configurations, and potentially refactoring components to use newer APIs.

[Copilot]

The react-native-windows upgrade from 0.63.0-0 to 0.65.0 may not be compatible with the React Native 0.69.12 upgrade. Verify that react-native-windows 0.65.0 supports React Native 0.69.x, as version mismatches can cause build failures.

Suggested change

	"react-native-windows": "^0.65.0",
	"react-native-windows": "^0.69.0",