chore(deps): bump react-cookie from 7.2.2 to 8.0.1#5731
chore(deps): bump react-cookie from 7.2.2 to 8.0.1#5731dependabot[bot] merged 4 commits intomainfrom
Conversation
28b35d1 to
5858fc1
Compare
There was a problem hiding this comment.
Requesting a review from @codemist and @Vinnl because of the changes added in 3149fb8:
We’ve been missing the CookiesProvider resulting in the error Missing <CookiesProvider> for this version bump. Detection has been added with react-cookie v8.0.0 with bendotcodes/cookies#862.
|
Preview URL 🚀 : https://blurts-server-pr-5731-mgjlpikfea-uk.a.run.app |
There was a problem hiding this comment.
Sorry Florian, I had not seen that this Dependabot notification email actually mentioned me directly. Changes look good, though I added two small changes on top: I moved it deeper in the hierarchy in case it rerenders more often, and aligned the API with our other context providers.
One also wonders what this actually does, given that our application worked anyway 😅 (I'm not actually convinced we need a separate React library for this anyway.)
@dependabot merge
Bumps [react-cookie](https://github.com/bendotcodes/cookies) from 7.2.2 to 8.0.1. - [Release notes](https://github.com/bendotcodes/cookies/releases) - [Changelog](https://github.com/bendotcodes/cookies/blob/main/LEGACY-CHANGELOG.md) - [Commits](bendotcodes/cookies@v7.2.2...v8.0.1) --- updated-dependencies: - dependency-name: react-cookie dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
I'm not sure whether it re-renders every time cookies change, but in case they do, this at least prevens the more static context providers from re-rendering as well.
Specifically, use a named export, and pass on *all* props, in case the upstream API changes.
1bd5f00 to
0ec58bf
Compare
Bumps react-cookie from 7.2.2 to 8.0.1.
Release notes
Sourced from react-cookie's releases.
... (truncated)
Commits
0d81f2eRelease v8.0.1 (#879)1cf45e2Bump major version for universal-cookie on dependency (#878)7a90c3cchore(deps): update dependency@types/reactto ^19.0.11 (#877)f3b9a9fchore(deps): update dependency@playwright/testto ^1.51.1 (#876)e9e999achore(deps): update dependency rollup to ^4.36.0 (#875)ae6738dchore(deps): lock file maintenance (#874)86315e6Release v8.0.0 (#867)7447fe9chore(deps): update dependency typescript to ^5.8.2 (#869)ba511afchore(deps): update dependency@types/expressto v5 (#871)4d0cbecchore(deps): update react monorepo (#870)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot will merge this PR once CI passes on it, as requested by @Vinnl.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)