Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update Font Awesome #86

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update Font Awesome #86

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 27, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@fortawesome/angular-fontawesome ^0.11.0 -> ^0.15.0 age adoption passing confidence
@fortawesome/fontawesome-svg-core (source) 6.5.1 -> 6.7.1 age adoption passing confidence
@fortawesome/free-brands-svg-icons (source) 6.5.1 -> 6.7.1 age adoption passing confidence
@fortawesome/free-regular-svg-icons (source) 6.5.1 -> 6.7.1 age adoption passing confidence
@fortawesome/free-solid-svg-icons (source) 6.5.1 -> 6.7.1 age adoption passing confidence

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.

v0.12.1

Compare Source

Added

v0.12.0

Compare Source

Make sure to check upgrade instructions.

Added
  • Support for Angular 15.
  • Documentation and option in ng-add schematic to use new Sharp Solid icons style.
Changed
  • Documentation on how to create fa-icon programmatically updated to not use deprecated ComponentFactoryResolver.
Deprecated
  • classes and styles inputs on all components are deprecated for removal as confusing and generally not useful. See upgrade instructions for the suggested migration path.
Removed
  • Angular 14.x is no longer supported. If you are using this version, please, stick with version 0.11.1.
FortAwesome/Font-Awesome (@​fortawesome/fontawesome-svg-core)

v6.7.1

Compare Source

v6.7.0

Compare Source

v6.6.0

Compare Source

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

v6.5.2

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: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

@netlify Netlify
Copy link

netlify bot commented Jan 27, 2024 •
edited
Loading

❌ Deploy Preview for super-kitsune-8d7875 failed. Why did it fail? →

Name Link
🔨 Latest commit a30222f
🔍 Latest deploy log https://app.netlify.com/sites/super-kitsune-8d7875/deploys/673e499da253d70008a7e29b

@renovate renovate bot changed the title Update dependency @fortawesome/angular-fontawesome to ^0.14.0 Update Font Awesome Apr 2, 2024
@renovate renovate bot force-pushed the renovate/font-awesome branch 2 times, most recently from 582852a to 6616041 Compare April 21, 2024 08:03
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Apr 25, 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: ui/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: ui@0.0.0
npm ERR! Found: @angular/core@14.3.0
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"^14.1.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"^17.0.0" from @fortawesome/angular-fontawesome@0.14.1
npm ERR! node_modules/@fortawesome/angular-fontawesome
npm ERR!   @fortawesome/angular-fontawesome@"^0.14.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-04-25T08_29_16_704Z-debug-0.log

@renovate renovate bot force-pushed the renovate/font-awesome branch 2 times, most recently from 9976e1c to b7792d0 Compare July 21, 2024 13:16
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Nov 20, 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: ui/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: ui@0.0.0
npm ERR! Found: @angular/core@14.3.0
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"^14.1.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/core@"^18.0.0" from @fortawesome/angular-fontawesome@0.15.0
npm ERR! node_modules/@fortawesome/angular-fontawesome
npm ERR!   @fortawesome/angular-fontawesome@"^0.15.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-20T20_41_57_784Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants