[Snyk] Upgrade expo-symbols from 0.2.2 to 0.4.5 #12
Conversation
Snyk has created this PR to upgrade expo-symbols from 0.2.2 to 0.4.5. See this package in npm: expo-symbols See this project in Snyk: https://app.snyk.io/org/chirag127/project/17310c6d-296d-4441-aa51-943dec153281?utm_source=github&utm_medium=referral&page=upgrade-pr
|
Keep this PR in a mergeable state → Learn moreAll Green is an AI agent that automatically: ✅ Addresses code review comments ✅ Fixes failing CI checks ✅ Resolves merge conflicts |
|
Important Review skippedIgnore keyword(s) in the title. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
Summary of ChangesHello @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-symbols' package to its latest stable version, '0.4.5'. This proactive upgrade aims to maintain the project's dependencies, ensuring it benefits from recent improvements and mitigates potential security vulnerabilities by staying current with the package ecosystem. Highlights
Using Gemini Code AssistThe 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
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 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
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request, automatically generated by Snyk, upgrades the expo-symbols dependency from version 0.2.2 to 0.4.5. The changes are straightforward, updating package.json and package-lock.json. The PR also helpfully aligns version specifiers for several other dependencies between package.json and package-lock.json.
However, I've noticed that this alignment introduced a new inconsistency for the expo-symbols package itself. I've left a comment with a suggestion to resolve this, which will improve dependency management consistency.
| "expo-splash-screen": "~0.30.10", | ||
| "expo-status-bar": "~2.0.1", | ||
| "expo-symbols": "~0.2.2", | ||
| "expo-symbols": "~0.4.5", |
There was a problem hiding this comment.
There's an inconsistency in the version specifier for expo-symbols between package.json (~0.4.5) and package-lock.json (^0.4.5). This seems to be an accidental introduction, as other parts of this PR align the specifiers in package-lock.json to use ~ as defined in package.json.
To resolve this, you could either change the specifier here to ^0.4.5 to match the lockfile (which is a common best practice for libraries following semantic versioning), or regenerate package-lock.json to match the ~ specifier. I'm suggesting the former for better dependency flexibility.
| "expo-symbols": "~0.4.5", | |
| "expo-symbols": "^0.4.5", |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Snyk has created this PR to upgrade expo-symbols from 0.2.2 to 0.4.5.
ℹ️ 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 25 versions ahead of your current version.
The recommended version was released 6 months ago.
Release notes
Package name: expo-symbols
-
0.4.5 - 2025-06-04
-
0.4.4 - 2025-04-30
-
0.4.3 - 2025-04-25
-
0.4.2 - 2025-04-14
-
0.4.1 - 2025-04-09
-
0.4.0 - 2025-04-08
-
0.3.1-canary-20250408-7f0ab53 - 2025-04-08
-
0.3.1-canary-20250407-10a9b42 - 2025-04-07
-
0.3.0 - 2025-04-04
-
0.2.3-canary-20250404-87e2506 - 2025-04-04
-
0.2.3-canary-20250404-42b6263 - 2025-04-04
-
0.2.3-canary-20250404-3c3b5fd - 2025-04-04
-
0.2.3-canary-20250403-13261ac - 2025-04-02
-
0.2.3-canary-20250402-161f57b - 2025-04-02
-
0.2.3-canary-20250331-817737a - 2025-03-31
-
0.2.3-canary-20250320-7a205d3 - 2025-03-20
-
0.2.3-canary-20250306-d9d3e02 - 2025-03-06
-
0.2.3-canary-20250305-0af9ad2 - 2025-03-05
-
0.2.3-canary-20250304-f08e984 - 2025-03-04
-
0.2.3-canary-20250304-8a21aa7 - 2025-03-04
-
0.2.3-canary-20250304-0da3971 - 2025-03-04
-
0.2.3-canary-20250303-4dba60e - 2025-03-03
-
0.2.3-canary-20250221-ef26fed - 2025-02-21
-
0.2.3-canary-20250219-4a5dade - 2025-02-19
-
0.2.3-canary-20250207-8bc5146 - 2025-02-07
-
0.2.2 - 2025-01-31
from expo-symbols GitHub release notesImportant
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: