Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Nov 23, 2024

This PR contains the following updates:

Package Change Age Confidence
@fortawesome/angular-fontawesome ^0.15.0^4.0.0 age confidence
@fortawesome/fontawesome-svg-core (source) ^6.6.0^7.0.0 age confidence
@fortawesome/free-regular-svg-icons (source) ^6.6.0^7.0.0 age confidence
@fortawesome/free-solid-svg-icons (source) ^6.6.0^7.0.0 age confidence

Release Notes

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

v4.0.0

Compare Source

Added
  • Support for Angular 21.
Removed
  • Angular 20.x is no longer supported. If you are using this version, please, stick with version 3.0.0.

v3.0.0

Compare Source

The release should be backwards compatible with 2.x, but since we bump the major dependency on @fortawesome/fontawesome-svg-core to 7.0.0, it is a major release. Please open an issue if you find any incompatibilities.

Added
  • Support for Font Awesome 7.
Changed
  • Reverted the change from 2.0.0 making the icon property in fa-icon and fa-duotone-icon components required at compile-time.
  • Update documentation to use self-closing tags for fa-icon and fa-duotone-icon components.

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

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.
FortAwesome/Font-Awesome (@​fortawesome/fontawesome-svg-core)

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: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 added the chore(deps) label Nov 23, 2024
@renovate
Copy link
Author

renovate bot commented Nov 23, 2024

⚠️ 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.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: rbtech@1.0.0
npm error Found: @angular/core@18.2.0
npm error node_modules/@angular/core
npm error   @angular/core@"18.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/core@"^21.0.0" from @fortawesome/angular-fontawesome@4.0.0
npm error node_modules/@fortawesome/angular-fontawesome
npm error   @fortawesome/angular-fontawesome@"^4.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-02T17_04_01_931Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-02T17_04_01_931Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-font-awesome branch 15 times, most recently from 89f85dd to b69ee8b Compare November 30, 2024 03:10
@renovate renovate bot force-pushed the renovate/major-font-awesome branch 9 times, most recently from a560bd7 to 3ec587c Compare December 7, 2024 03:59
@renovate renovate bot force-pushed the renovate/major-font-awesome branch 4 times, most recently from 6954c92 to ddf0020 Compare December 10, 2024 19:04
@renovate renovate bot force-pushed the renovate/major-font-awesome branch 24 times, most recently from 0c20e2a to b9d32bc Compare June 26, 2025 18:04
@renovate renovate bot force-pushed the renovate/major-font-awesome branch from b9d32bc to 3ea9b30 Compare June 26, 2025 21:55
@renovate renovate bot force-pushed the renovate/major-font-awesome branch from 3ea9b30 to dbf2154 Compare July 22, 2025 20:47
@renovate renovate bot changed the title fix(deps): update dependency @fortawesome/angular-fontawesome to v2 fix(deps): update font awesome (major) Jul 22, 2025
@renovate renovate bot force-pushed the renovate/major-font-awesome branch from dbf2154 to db31628 Compare August 7, 2025 11:02
@renovate renovate bot force-pushed the renovate/major-font-awesome branch from db31628 to 2a26e23 Compare November 25, 2025 00:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants