-
Notifications
You must be signed in to change notification settings - Fork 158
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(deps): update dependency next to v14.2.21 #372
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/nextjs-monorepo
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/nextjs-monorepo
branch
from
December 3, 2024 17:06
16e8944
to
5e562d8
Compare
renovate
bot
changed the title
fix(deps): update dependency next to v14.2.19
fix(deps): update dependency next to v14.2.20
Dec 4, 2024
renovate
bot
force-pushed
the
renovate/nextjs-monorepo
branch
from
December 4, 2024 21:21
5e562d8
to
a9ac3d6
Compare
renovate
bot
force-pushed
the
renovate/nextjs-monorepo
branch
from
December 5, 2024 16:25
a9ac3d6
to
ef997bc
Compare
renovate
bot
force-pushed
the
renovate/nextjs-monorepo
branch
from
December 19, 2024 11:44
ef997bc
to
7668ea6
Compare
renovate
bot
changed the title
fix(deps): update dependency next to v14.2.20
fix(deps): update dependency next to v14.2.21
Dec 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
14.2.18
->14.2.21
Release Notes
vercel/next.js (next)
v14.2.21
Compare Source
v14.2.20
Compare Source
v14.2.19
Compare Source
Core Changes
Misc Changes
Credits
Huge thanks to @ztanner and @ijjk for helping!
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.
This PR was generated by Mend Renovate. View the repository job log.