-
Notifications
You must be signed in to change notification settings - Fork 148
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
chore(deps): update peerdependency @vercel/kv to v1 #334
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #334 +/- ##
==========================================
- Coverage 65.05% 64.26% -0.80%
==========================================
Files 39 42 +3
Lines 4055 4105 +50
Branches 487 490 +3
==========================================
Hits 2638 2638
- Misses 1408 1455 +47
- Partials 9 12 +3 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/vercel-kv-1.x
branch
from
November 14, 2023 16:55
1486571
to
6430f07
Compare
renovate
bot
force-pushed
the
renovate/vercel-kv-1.x
branch
from
November 27, 2023 14:09
6430f07
to
66250e9
Compare
renovate
bot
force-pushed
the
renovate/vercel-kv-1.x
branch
from
December 7, 2023 01:42
66250e9
to
32519c6
Compare
renovate
bot
force-pushed
the
renovate/vercel-kv-1.x
branch
from
December 8, 2023 10:22
32519c6
to
87810c1
Compare
renovate
bot
force-pushed
the
renovate/vercel-kv-1.x
branch
from
December 13, 2023 12:14
87810c1
to
5842f58
Compare
renovate
bot
force-pushed
the
renovate/vercel-kv-1.x
branch
from
December 18, 2023 01:19
5842f58
to
45c5202
Compare
renovate
bot
force-pushed
the
renovate/vercel-kv-1.x
branch
from
January 12, 2024 01:47
45c5202
to
61276e7
Compare
renovate
bot
force-pushed
the
renovate/vercel-kv-1.x
branch
from
January 12, 2024 11:10
61276e7
to
a631915
Compare
renovate
bot
force-pushed
the
renovate/vercel-kv-1.x
branch
from
January 18, 2024 01:15
a631915
to
1abe4c9
Compare
renovate
bot
force-pushed
the
renovate/vercel-kv-1.x
branch
from
March 4, 2024 16:12
1abe4c9
to
d37e830
Compare
Deploying with Cloudflare Pages
|
renovate
bot
force-pushed
the
renovate/vercel-kv-1.x
branch
from
March 4, 2024 16:17
d37e830
to
7358e80
Compare
renovate
bot
force-pushed
the
renovate/vercel-kv-1.x
branch
from
March 14, 2024 11:56
7358e80
to
635e40d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.2.4
->^1.0.1
Release Notes
vercel/storage (@vercel/kv)
v1.0.1
Compare Source
Patch Changes
44f84bd
: Upgrade to latest upstash-redis: https://github.com/upstash/upstash-redis/releasesv1.0.0
Compare Source
Major Changes
d85bb76
: feat(kv): Switch todefault
for fetchcache
optionBREAKING CHANGE: When using Next.js and vercel/kv, you may have kv requests and/or Next.js resources using kv being cached when you don't want them to.
If that's the case, then opt-out of caching with
https://nextjs.org/docs/app/api-reference/functions/unstable_noStore.
On the contrary, if you want to enforce caching of resources you can use https://nextjs.org/docs/app/api-reference/functions/unstable_cache.
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 these updates again.
This PR has been generated by Mend Renovate. View repository job log here.