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

fix: update dependency history to v5 (release-bot/next-v15.x) #1997

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 4, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
history ^4.10.1 -> ^5.0.0 age adoption passing confidence

Release Notes

ReactTraining/history

v5.0.1

Compare Source

This patch release contains a tiny TypeScript update to use the built-in Partial utility for PartialPath and PartialLocation. We always love it when we can ship just a little less code!

🙏 Credits

Thanks to @​liuhanqu, @​hanquliu, @​chaance and @​mjackson for your contributions!

v5.0.0

Compare Source

Today we are very pleased to announce the stable release of history version 5!

Overview

This version includes many enhancements and fixes a few important issues with the library.

New Features
  • Hash history now has support for location.state
  • Better history.block API, with support for retrying transitions
  • Full TypeScript declarations and IntelliSense docs
  • Adds development and production builds for <script type=module> users
  • Both browser and hash history have support for iframes (custom window objects)
  • About 50% smaller than v4 (and no dependencies)
Bugfixes
  • Fixed some long-standing encoding issues with location.pathname
  • Removed unfixable warnings about pushing the same path in hash history
  • Renamed browser global to HistoryLibrary so it doesn't conflict with window.History
Breaking Changes
  • Removed support for browsers that do not support the HTML5 history API (no pushState)
  • Removed relative pathname support in hash history and memory history
  • Removed getUserConfirmation, keyLength, and hashType APIs

Usage

Please refer to our installation guide for instructions about how to install the library.

There is also a getting started guide as well as a complete API reference in the docs folder.

We are very excited about this release, especially because it will serve as the foundation for the upcoming release of React Router version 6.

Thank you for your support. Enjoy! 😀


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot added the 📦 v15 Apply this label to a pull request, if it has to be cherry-picked to the v15.x-branch after merging. label Oct 4, 2021
@renovate renovate bot force-pushed the renovate/release-bot/next-v15.x-history-5.x branch from a2291e5 to 4c14f69 Compare October 11, 2021 10:34
@robertkowalski
Copy link
Contributor

remix-run/history#811

@robertkowalski
Copy link
Contributor

remix-run/history#812

@robertkowalski
Copy link
Contributor

  1. there is no equivalent for basename any more

@robertkowalski
Copy link
Contributor

lets wait for react-router 6 then

@robertkowalski robertkowalski deleted the renovate/release-bot/next-v15.x-history-5.x branch October 27, 2021 13:13
@renovate
Copy link
Contributor Author

renovate bot commented Oct 27, 2021

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📦 v15 Apply this label to a pull request, if it has to be cherry-picked to the v15.x-branch after merging.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants