fix(deps): update dependency @fortawesome/angular-fontawesome to v2 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@fortawesome/angular-fontawesome	^0.14.0 -> ^2.0.0

---

Release Notes

FortAwesome/angular-fontawesome (@​fortawesome/angular-fontawesome)

v2.0.1

Compare Source

Fixed

• Restored possibility to set inputs to undefined.

v2.0.0

Compare Source

Converted all library internal component implementation to use reactive Signal APIs.

Make sure to check upgrade instructions.

Added

• Support for Angular 20.
• Documentation on changes in Programmatic API.
• Documentation for upgrading 1.0.0 to 2.0.0
• Updated code to use signal APIs like signal, computed, effect, input, model.
• Updated changeDetection: ChangeDetectionStrategy.OnPush 🚀 for all components.

Removed

• Deprecated the render function from the FaIconComponent.
• Programmatic API has changed, please refer here and migration guide 1.0.0 to 2.0.0

v1.0.0

Compare Source

There are no major changes in this release. The version bump is to signal that the library is stable now and no major breaking changes are expected in the future.

Added

• Support for Angular 19.
• All available icon packages to the ng-add schematic.
• Possibility to specify custom rotate value for fa-icon and fa-duotone-icon components.

Removed

• Angular 18.x is no longer supported. If you are using this version, please, stick with version 0.15.0.

v0.15.0

Compare Source

Make sure to check upgrade instructions.

Added

• Support for Angular 18.
• Documentation on how to use NPM Kit packages.
• Documentation on how to correctly use fa-stack in standalone components.
• Documentation on how to use custom icons.
• FAQ page with considerations on whether to use this library.
• Configuration option for the FontAwesomeTestingModule to not throw errors when adding icons.
• Documentation on how to add global styles to the page.

Fixed

• Documentation for the rotate input.
• Global styles are now correctly added to the page in SSR context.

Changed

• icon input type is now more permissive.
• @fortawesome/fontawesome-svg-core became a regular dependency.

Removed

• Angular 17.x is no longer supported. If you are using this version, please, stick with version 0.14.1.
• Deprecated inputs spin and pulse. Use animation input instead.
• Deprecated inputs styles and classes.

---

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 is behind base branch, 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.

---

Thanks for the PR!

Deployments, as required, will be available below:

• api
• admin
• public

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts 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: public/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: fom-public@0.0.1
npm error Found: @angular/core@17.3.12
npm error node_modules/@angular/core
npm error   @angular/core@"^17.3.12" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/core@"^20.0.0" from @fortawesome/angular-fontawesome@2.0.1
npm error node_modules/@fortawesome/angular-fontawesome
npm error   @fortawesome/angular-fontawesome@"^2.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/2025-07-11T22_36_47_643Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-07-11T22_36_47_643Z-debug-0.log

File name: admin/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: fom-admin@0.0.1
npm error Found: @angular/core@17.3.12
npm error node_modules/@angular/core
npm error   @angular/core@"^17.3.12" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/core@"^20.0.0" from @fortawesome/angular-fontawesome@2.0.1
npm error node_modules/@fortawesome/angular-fontawesome
npm error   @fortawesome/angular-fontawesome@"^2.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/2025-07-11T22_36_51_853Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-07-11T22_36_51_853Z-debug-0.log