Skip to content

fix(deps): update font awesome to v7 - #187

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-font-awesome
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-font-awesome

Conversation

@renovate

@renovate renovate Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@fortawesome/fontawesome-svg-core (source) ^6.5.1^7.0.0 age confidence
@fortawesome/free-solid-svg-icons (source) ^6.5.1^7.0.0 age confidence

Release Notes

FortAwesome/Font-Awesome (@​fortawesome/fontawesome-svg-core)

v7.3.1

Compare Source

Change log available at https://fontawesome.com/docs/changelog/

v7.3.0

Compare Source

v7.2.0

Compare Source

Change log available at https://fontawesome.com/changelog

v7.1.0

Compare Source

Change log available at https://fontawesome.com/docs/changelog/

v7.0.1

Compare Source

Change log available at https://fontawesome.com/docs/changelog/

v7.0.0

Compare Source

Change log available at https://fontawesome.com/docs/changelog/


Configuration

📅 Schedule: (UTC)

  • 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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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

renovate Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @fortawesome/vue-fontawesome@3.0.8
npm error Found: @fortawesome/fontawesome-svg-core@7.3.1
npm error node_modules/@fortawesome/fontawesome-svg-core
npm error   @fortawesome/fontawesome-svg-core@"^7.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @fortawesome/fontawesome-svg-core@"~1 || ~6" from @fortawesome/vue-fontawesome@3.0.8
npm error node_modules/@fortawesome/vue-fontawesome
npm error   @fortawesome/vue-fontawesome@"^3.0.5" from the root project
npm error
npm error Conflicting peer dependency: @fortawesome/fontawesome-svg-core@6.7.2
npm error node_modules/@fortawesome/fontawesome-svg-core
npm error   peer @fortawesome/fontawesome-svg-core@"~1 || ~6" from @fortawesome/vue-fontawesome@3.0.8
npm error   node_modules/@fortawesome/vue-fontawesome
npm error     @fortawesome/vue-fontawesome@"^3.0.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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-09-14T09_42_58_476Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-14T09_42_58_476Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/major-font-awesome branch from 5a9078e to a3c5936 Compare September 7, 2026 14:40
@renovate
renovate Bot force-pushed the renovate/major-font-awesome branch from a3c5936 to 063f634 Compare September 14, 2026 09:43
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