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.

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

[Snyk] Upgrade @fortawesome/fontawesome-free from 5.10.2 to 5.12.1 #1

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

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Apr 5, 2020

Snyk has created this PR to upgrade @fortawesome/fontawesome-free from 5.10.2 to 5.12.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
  • The recommended version is 7 versions ahead of your current version.
  • The recommended version was released 2 months ago, on 2020-02-05.
Release notes
Package name: @fortawesome/fontawesome-free
  • 5.12.1 - 2020-02-05

    Added

    Changed

    • Do not separate web fonts files for Free Kits
    • The .fab CSS class now has explicit weight of 400 instead of inheriting 'normal'
    • Balance the plus symbol in file-plus and folder-plus #16004
    • Removed cross from coffin (new coffin-cross still available) #15646
    • Updated edge brand icon #15771
    • Updated clock hands #15779

    Fixed

    • Guard against run-away pseudo element searching with String.codePointAt ponyfill
    • Silence errors when using the conflict detector
  • 5.12.0 - 2019-12-10

    Added

    • New science fiction and household icons
    • Metadata in Yaml format now available in JS packages
      @fortawesome/fontawesome-free and @fortawesome/fontawesome-pro

    Changed

    • Updated twitch, safari, pied-piper, and android brand icon
    • Renaming haykal icon to bahai
    • Added "sideEffects: false" to JS icon packages to aid with tree-shaking

    Fixed

    • Improved eye position on the dog icon
    • Updated solid style of the shape icon
    • Adding missing versions for balance-scale-left and balance-scale-right icons
    • Corrected missing cut-outs for envelope-open-dollar and envelope-open-text
      which made swap opacity incorrect
    • Fixing icon mismatch for contract and expand icons in the version 4 shim
    • TypeScript definition includes optional params for layer() API call
    • Symbols can now be inserted using Windows Character Map, Word, and PowerPoint
      #14614
    • Correcting the LICENSE.txt for @fortawesome/fontawesome-svg-core and
      @fortawesome/fontawesome-common-types
  • 5.12.0-2 - 2019-12-10
  • 5.12.0-1 - 2019-11-06
  • 5.11.2 - 2019-09-23

    Changed

    • Updated laravel brand icon

    Fixed

    • New scanner-image icon was using the same unicode value as scanner causing overlapped icons
    • The film-canister icon was incorrectly spelled film-cannister
  • 5.11.1 - 2019-09-18

    Fixed

    • Duotone icons updated in 5.11.0 had incorrect attribute order which caused
      them to fail to load for all kits
  • 5.11.0 - 2019-09-18

    Added

    • New tech, music, and western-themed icons
    • Added umbraco, swift, orcid, mdb (and one more surprise) brand icons

    Fixed

    • SVG with JavaScript no longer duplicates the id attribute when in nesting mode
    • Corrected inconsistencies with the send-back and send-backward icons
    • Corrected inconsistencies with duotone icon viewBox widths that did not match
      the solid style
  • 5.10.2 - 2019-08-22

    Added

    • SVG with JS API function layers() now accepts params to add additional classes

    Changed

    • Lots of updates to various duotone icons
    • Updated the keybase brand icon

    Fixed

from @fortawesome/fontawesome-free GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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.

1 participant