Repository navigation
release: v4.29.1 - pass --ignore-scripts on the default publish command - #322
Merged
Merged
Conversation
The publish jobs run the generated command inside the downloaded package-contents/ artifact: npm-pack output with no node_modules and no lockfile. npm/pnpm/yarn publish still fire prepack/prepublishOnly/postpack there, so a repo whose prepack runs a real build (e.g. tsup behind "prepack": "npm run build") re-runs it in a directory that can't supply its devDependencies and the publish dies with `tsup: not found` (exit 127) — CLDMV/vitest-runner v1.4.0 failed both registries this way. build_command already ran in the build job before packing, so no lifecycle script has work left at publish time. Add --ignore-scripts to the default command for both npm and GitHub Packages, for every package manager. A caller-supplied publish_command / github_packages_publish_command is still used verbatim. The command was built in three places — repo-detection (the one the reusable workflow actually uses, core and satellites) plus the publish-npm / publish-github-packages fallbacks — kept in sync by comment. Move it into one shared buildPublishCommand() in npm/utilities/publish-command with unit tests, so the flag can't drift between them. Document the artifact publish contract and the custom command caveat in docs/conventions/package-manager.md. Fixes #320
cldmv-bot
Bot
added
! release → master
Shinrai
approved these changes
Sep 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 What's Changed
💥 Breaking Changes
No breaking changes
✨ Features
No new features
🐛 Bug Fixes
📦 Dependencies
No dependency updates
🔧 Other Changes
No other changes
👥 Contributors
Co-authored-by: Shinrai Shinrai@users.noreply.github.com