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 react-leaflet from 3.0.5 to 3.2.5 #4

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

masterrob94
Copy link

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade react-leaflet from 3.0.5 to 3.2.5.

ℹ️ 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 years ago, on 2022-01-15.
Release notes
Package name: react-leaflet
  • 3.2.5 - 2022-01-15

    Fix supporting mutable whenCreated with unmounting MapContainer.

  • 3.2.4 - 2022-01-09

    Fix removing the map handlers when MapContainer is unmounted.

  • 3.2.3 - 2022-01-08
  • 3.2.2 - 2021-10-09

    Fix layer unmount (PR #916 by piitaya).

  • 3.2.1 - 2021-08-01
    • Fix Popup unmounting logic to unbind from container.
    • Fix links to point to Leaflet 1.7.1 docs (PR #889 by zerekw).
  • 3.2.0 - 2021-05-15
    • Change unmounting logic for some layers, which should fix issues related to removing or updating elements.
    • Make the style prop of GeoJSON mutable, this prop should be used instead of pathOptions (pathOptions can still be used but should be considered deprecated).
    • Fix documentation about bounds prop being an instance of LatLngBounds.
  • 3.1.0 - 2021-01-30
  • 3.0.5 - 2020-12-19

    Use useState hook rather than useMemo to store immutable values in MapContainer and Pane.

from react-leaflet 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

markszutor and others added 3 commits October 24, 2023 13:49
This commit was made to satisfy the OCD of not having different numbers in files that are calling upon the same information.
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.

3 participants