fix(deps): update dependency @fortawesome/angular-fontawesome to ^0.15.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@fortawesome/angular-fontawesome	^0.12.0 -> ^0.15.0

---

Release Notes

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

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.

v0.14.1

Compare Source

Fixed

• Removed import from @fortawesome/fontawesome-common-types, which was an undeclared dependency.

v0.14.0

Compare Source

Added

• Support for Angular 17.
• Possibility to use all components as standalone.

Changed

• Examples to use standalone components instead of modules.

Removed

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

v0.13.0

Compare Source

Added

• Support for Angular 16.

Removed

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

---

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!

Any successful deployments (not always required) will be available below.

• api
• admin
• public

Once merged, code will be promoted and handed off to following workflow run.

• Main 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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: @angular/[email protected]
npm error node_modules/@angular/core
npm error   @angular/core@"^15.2.9" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/core@"^18.0.0" from @fortawesome/[email protected]
npm error node_modules/@fortawesome/angular-fontawesome
npm error   @fortawesome/angular-fontawesome@"^0.15.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 /tmp/renovate/cache/others/npm/_logs/2025-01-06T22_06_58_263Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-06T22_06_58_263Z-debug-0.log

File name: admin/package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: @angular/[email protected]
npm error node_modules/@angular/core
npm error   @angular/core@"^15.2.9" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/core@"^18.0.0" from @fortawesome/[email protected]
npm error node_modules/@fortawesome/angular-fontawesome
npm error   @fortawesome/angular-fontawesome@"^0.15.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 /tmp/renovate/cache/others/npm/_logs/2025-01-06T22_07_02_250Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-06T22_07_02_250Z-debug-0.log

[DerekRoberts]

Angular updates are being handled by @ianliuwk1019 in another PR.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (^0.15.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.