Skip to content

fix(core): do not follow symlinks when creating remote cache tarball#31138

Merged
AgentEnder merged 1 commit intonrwl:masterfrom
ianldgs:fix-remote-cache-symlinks
May 10, 2025
Merged

fix(core): do not follow symlinks when creating remote cache tarball#31138
AgentEnder merged 1 commit intonrwl:masterfrom
ianldgs:fix-remote-cache-symlinks

Conversation

@ianldgs
Copy link
Copy Markdown
Contributor

@ianldgs ianldgs commented May 8, 2025

Current Behavior

Symlinks in the remote cache tarball are "followed". That modifies the output of Next.js projects using pnpm, causing a restored cache not to work in production.

Expected Behavior

Symlinks are added to the tarball, instead of being followed. I.e. the cache output is not modified.

Related Issue(s)

Should fix #31085.

@ianldgs ianldgs requested review from a team as code owners May 8, 2025 22:06
@ianldgs ianldgs requested review from JamesHenry and xiongemi May 8, 2025 22:06
@vercel
Copy link
Copy Markdown

vercel Bot commented May 8, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Updated (UTC)
nx-dev ⬜️ Ignored (Inspect) Visit Preview May 9, 2025 1:24am

@nx-cloud
Copy link
Copy Markdown
Contributor

nx-cloud Bot commented May 8, 2025

View your CI Pipeline Execution ↗ for commit c572037.

Command Status Duration Result
nx affected --targets=lint,test,build,e2e,e2e-c... ✅ Succeeded 37m 10s View ↗
nx run-many -t check-imports check-commit check... ✅ Succeeded 14s View ↗
nx-cloud record -- nx-cloud conformance:check ✅ Succeeded 2s View ↗
nx-cloud record -- nx format:check ✅ Succeeded 1s View ↗
nx-cloud record -- nx sync:check ✅ Succeeded 1s View ↗
nx documentation ✅ Succeeded 46s View ↗

☁️ Nx Cloud last updated this comment at 2025-05-09 02:06:51 UTC

@ianldgs ianldgs force-pushed the fix-remote-cache-symlinks branch from ec77bac to c572037 Compare May 9, 2025 01:21
@ianldgs
Copy link
Copy Markdown
Contributor Author

ianldgs commented May 9, 2025

@AgentEnder or @FrozenPandaz I know the code owners already auto-assigned some reviewers, but I think you guys are more up-to-date with this part. Could any of you take a look please?

@FrozenPandaz FrozenPandaz added the priority: high High Priority (important issues which affect many people severely) label May 9, 2025
@ianldgs
Copy link
Copy Markdown
Contributor Author

ianldgs commented May 9, 2025

Tested this locally by publishing nx from this branch to our internal npm registry and using a pnpm override.
Can confirm it fixes #31085 for us.

@AgentEnder AgentEnder merged commit cbb2619 into nrwl:master May 10, 2025
7 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators May 16, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

priority: high High Priority (important issues which affect many people severely)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Next.js standalone output broken (again) when remote cached due to missing PNPM symlinks

3 participants