Skip to content

Bump tar from 7.5.7 to 7.5.16 in /packages/create-next-app #33

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.

Sign up for GitHub

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

Open
dependabot wants to merge 1 commit into
base: canary
Choose a base branch
from
Open

Bump tar from 7.5.7 to 7.5.16 in /packages/create-next-app #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/create-next-app/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@
"picocolors": "1.1.1",
"prettier-plugin-tailwindcss": "0.6.2",
"prompts": "2.4.2",
"tar": "7.5.7",
"tar": "7.5.16",

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep pnpm-lock.yaml in sync with tar bump

This manifest now asks for tar@7.5.16, but pnpm-lock.yaml still records packages/create-next-app with tar specifier/version 7.5.7 at lines 1013-1015. The Build packages workflow runs pnpm install --frozen-lockfile (.github/workflows/build_and_deploy.yml:554), and pnpm documents that this mode does not update the lockfile and fails when the lockfile is out of sync with the manifest (https://pnpm.io/cli/install#--frozen-lockfile). Please regenerate and commit the lockfile entry with this bump so CI and frozen installs can proceed.

Useful? React with 👍 / 👎.

"update-check": "1.5.4",
"validate-npm-package-name": "5.0.1"
},
Expand Down