chore(deps): bump loader-utils and next #36
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.
Bumps loader-utils to 1.4.1 and updates ancestor dependency next. These dependencies need to be updated together.
Updates
loader-utils
from 1.4.0 to 1.4.1Release notes
Sourced from loader-utils's releases.
Changelog
Sourced from loader-utils's changelog.
Commits
8f082b3
chore(release): 1.4.14504e34
fix: security problem (#220)Updates
next
from 9.4.4 to 13.0.2Release notes
Sourced from next's releases.
... (truncated)
Commits
2f9efb1
v13.0.23cb0c29
v13.0.2-canary.3eb0d9f5
Remove static generation bail-out from usePathname (#42440)c0a8c88
Fix undici warning showing unexpectedly (#42444)0eed107
Fix invalid markdown lang (#42442)1f55ba3
ChangeusePathname
to returnstring | null
(#42380)e74de1a
Clarify app and pages file conflicting files (#42415)21b6654
Do not strip loader arg in dynamic for server components (#42426)152f51c
Avoid breaking useRouter() type change (#42430)8fa78a5
Google fonts single request (#42406)Maintainer changes
This version was pushed to npm by vercel-release-bot, a new releaser for next since your current version.
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 commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will 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 version
will 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 dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and languageYou can disable automated security fix PRs for this repo from the Security Alerts page.