Update dependency next-usequerystate to v1.17.4
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| next-usequerystate (source) | 1.15.4 -> 1.17.4 |
Release Notes
47ng/nuqs (next-usequerystate)
v1.17.4
Bug Fixes
v1.17.3
Bug Fixes
v1.17.2
Bug Fixes
- Don't rely on URL for initial state (9912eef)
v1.17.1
Bug Fixes
v1.17.0
Features
v1.16.1
Bug Fixes
- Sync with useSearchParams in 14.1.0 (#482) - Thanks @ianldgs, @aldenquimby, and @skve !
Full Changelog: https://github.com/47ng/nuqs/compare/v1.16.0...v1.16.1
v1.16.0
Features
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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| ding-one | ❌ Failed (Inspect) | May 14, 2024 0:33am |
Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword
link(e.g. "Link T-123").💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.
PR Summary
-
Updated
next-usequerystateversion inpackage.jsonThe version ofnext-usequerystateused in our application has been updated. This library helps our app maintain its state during navigation. The update from version 1.8.4 to 1.9.0 brings in new features and potential bug fixes which we can benefit from. -
Updated
next-usequerystateversion inpnpm-lock.yamlThis change helps us secure the specific version ofnext-usequerystatebeing used. This is important as it ensures every developer working on the project uses the same version, providing consistency across development workflows. It's been updated to match the version inpackage.json, from 1.8.4 to 1.9.0.