🐛 Fixed production builds using unpinned dependencies#28240
Conversation
ref #28205 The pnpm 11 archive flow dropped root workspace overrides from the packaged workspace, so production installs resolved a different dependency graph than the source workspace. Keeping overrides in the deploy workspace preserves the intended dependency policy while still regenerating a pnpm 11-compatible lockfile.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Walkthrough
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Actionable comments posted: 0 |
Summary
pnpm-workspace.yamloverridesandpackageExtensionsin the Ghost deploy archiveWhy
The pnpm 11 archive flow was writing a trimmed deploy workspace that dropped root overrides. That let production archives resolve a different dependency graph from the source workspace, including changed versions for packages such as
@tryghost/errors,moment-timezone,juice, and other transitive dependencies.Testing
CI=true pnpm --filter ghost archiveghost/core/ghost-6.42.1-rc.0.tgzand confirmedpnpm-workspace.yamlcontainscatalog,catalogs,overrides,packageExtensions, andminimumReleaseAge: 0CI=true pnpm install --prod --frozen-lockfile --ignore-scripts@tryghost/errors 1.3.13,moment-timezone 0.5.45, andjuice 9.1.0