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 swup from 4.7.0 to 4.8.1 #17

Closed

Conversation

joepdooper
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade swup from 4.7.0 to 4.8.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 2 versions ahead of your current version.

  • The recommended version was released on 23 days ago.

Release notes
Package name: swup
  • 4.8.1 - 2024-09-28
    • Fix usage of combined hook options once and replace
  • 4.8.0 - 2024-09-25
    • Add hooks option to allow registering all hooks at once
    • Add visit.meta object for custom data
  • 4.7.0 - 2024-07-18
    • Inherit data-swup-* attributes from parent elements
    • Store current location as object at swup.location
    • Deprecate swup.currentPageUrl in favor of swup.location.url
    • Make previous page's hash available at visit.from.hash
from swup GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

Snyk has created this PR to upgrade swup from 4.7.0 to 4.8.1.

See this package in npm:
swup

See this project in Snyk:
https://app.snyk.io/org/joepdooper/project/c65d7b12-eef5-4fe4-bb66-2078921c4a04?utm_source=github&utm_medium=referral&page=upgrade-pr
@joepdooper joepdooper closed this Dec 1, 2024
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.

2 participants