Skip to content

fix(deps): update dependency @expo/vector-icons to v15#93

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/expo-vector-icons-15.x
Open

fix(deps): update dependency @expo/vector-icons to v15#93
renovate[bot] wants to merge 1 commit intomainfrom
renovate/expo-vector-icons-15.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 29, 2025

This PR contains the following updates:

Package Change Age Confidence
@expo/vector-icons (source) ^14.0.4^15.0.0 age confidence

Release Notes

expo/vector-icons (@​expo/vector-icons)

v15.0.3

Compare Source

v15.0.2

Compare Source

v15.0.1

Compare Source

v15.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Sep 29, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: crux-frontend/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: crux-frontend@1.0.0
npm error Found: expo-font@13.3.2
npm error node_modules/expo-font
npm error   expo-font@"~13.3.0" from the root project
npm error   expo-font@"~13.3.2" from expo@53.0.27
npm error   node_modules/expo
npm error     expo@"^53.0.0" from the root project
npm error     peer expo@"*" from expo-font@13.3.2
npm error     2 more (@expo/dom-webview, @expo/metro-runtime)
npm error
npm error Could not resolve dependency:
npm error peer expo-font@">=14.0.4" from @expo/vector-icons@15.0.3
npm error node_modules/@expo/vector-icons
npm error   @expo/vector-icons@"^15.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-02-12T16_44_03_082Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-12T16_44_03_082Z-debug-0.log

@vercel
Copy link

vercel bot commented Sep 29, 2025

Deployment failed with the following error:

Resource is limited - try again in 2 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/wysrockets-projects?upgradeToPro=build-rate-limit

@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@renovate renovate bot force-pushed the renovate/expo-vector-icons-15.x branch from 128a43f to 749165b Compare October 21, 2025 10:50
@vercel
Copy link

vercel bot commented Oct 21, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
v0-thecrux Ready Ready Preview Comment Oct 21, 2025 10:50am

💡 Enable Vercel Agent with $100 free credit for automated AI reviews

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.

0 participants