Bump json5 and next in /web #38
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
riley/sanity-nextjs-landing-pages!38
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "dependabot/npm_and_yarn/web/json5-and-next-1.0.2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bumps json5 to 1.0.2 and updates ancestor dependency next. These dependencies need to be updated together.
Updates
json5from 1.0.1 to 1.0.2Release notes
Sourced from json5's releases.
Changelog
Sourced from json5's changelog.
... (truncated)
Commits
a62db1e1.0.2e0c23fedocs: update CHANGELOG for v1.0.262a6540fix: add proto to objects and arraysUpdates
nextfrom 8.1.0 to 13.1.1Release notes
Sourced from next's releases.
... (truncated)
Commits
4ac737ev13.1.1f0a8b7ev13.1.1-canary.1b0a1e99Fixnext/image404 whenbasePathandtrailingSlashdefined (#44312)f0aa10bRemove experimental for modularizeImports from docs and example (#44311)44548ddv13.1.1-canary.000b2113Fix CSS resource path not matched in__entry_css_files__(#44310)fd0d0f5Excludesrcsetfrom svg image (#44308)8a9133dUpdated dependencies forwith-tailwindcssexample (#44289)fd9ec64Use turbo for packing files in test setup (#44074)02489c2v13.1.0Maintainer 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 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 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)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill 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.
🛠️ CodeTether Fix
Picked up this request for PR #38 on branch
dependabot/npm_and_yarn/web/json5-and-next-1.0.2. I’m preparing the workspace and will push changes directly to the existing PR branch if the task succeeds. I will also make sure the branch is mergeable withmaster.🛠️ CodeTether Fix
Worker error after claim: Git command failed: fatal: detected dubious ownership in repository at '/workspace/repos/1497c85dcc391994'
To add an exception for this directory, call:
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.