Bump tar from 7.5.11 to 7.5.16 in /packages/next#34
Conversation
Bumps [tar](https://github.com/isaacs/node-tar) from 7.5.11 to 7.5.16. - [Release notes](https://github.com/isaacs/node-tar/releases) - [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md) - [Commits](isaacs/node-tar@v7.5.11...v7.5.16) --- updated-dependencies: - dependency-name: tar dependency-version: 7.5.16 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c951a31127
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "style-loader": "4.0.0", | ||
| "superstruct": "1.0.3", | ||
| "tar": "7.5.11", | ||
| "tar": "7.5.16", |
There was a problem hiding this comment.
Update the lockfile with the tar bump
This changes the packages/next manifest to require tar@7.5.16, but pnpm-lock.yaml still records the packages/next importer with tar specifier/version 7.5.11. In CI workflows that run pnpm install/pnpm install --frozen-lockfile, pnpm treats the lockfile as frozen and will reject the out-of-sync manifest instead of installing, so this dependency bump will block clean installs until the lockfile is regenerated and committed.
Useful? React with 👍 / 👎.
Bumps tar from 7.5.11 to 7.5.16.
Commits
cf213387.5.1621a8220do not apply PAX header fields to meta entries52632cfupdate project deps302f51ffix inconsequential typo in PENDINGLINKS symbol name55dbb99remove some uses of mutate-fs87cc3097.5.157aef486fix: regression in pending links detection6244eb37.5.149704d8cstricter protection against hardlinks preempting their targets700734fupdate workflows and depsDependabot 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 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)You can disable automated security fix PRs for this repo from the Security Alerts page.