Skip to content

release: v4.29.2 - pass --ignore-scripts on the default publish command - #324

Merged
cldmv-bot[bot] merged 6 commits into
masterfrom
next
Sep 28, 2026
Merged

cldmv-bot[bot] merged 6 commits into
masterfrom
next

Conversation

@cldmv-bot

@cldmv-bot cldmv-bot Bot commented Sep 28, 2026

Copy link
Copy Markdown
Contributor

🚀 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

Shinrai and others added 6 commits September 27, 2026 21:49
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
…just CI

The merge gate waits on every check-run on the release PR's head commit,
from any workflow, but the caller's workflow_run trigger only named the
CI workflow. Whichever workflow finishes last is the only one whose
completion can see a fully green head — and CodeQL routinely outlasts CI.

v4.29.1's release PR #322 got stuck exactly this way: approved at
05:00:03, CI finished at 05:00:10 and re-fired release-merge, which
logged "waiting on 1 unfinished check(s): 🔍 Analyze javascript-typescript"
and exited; CodeQL finished at 05:00:51, wasn't in the workflow_run list,
and nothing re-fired. (The approval's own pull_request_review run was
replaced in the concurrency group's pending slot by a later workflow_run
run — harmless, since every run re-reads approval and check state from
the API.)

List every workflow that puts a check on a release-PR head: this repo's
own local-* set in local-release-merge.yml, and the whole standard v4
template set in the release-merge.yml caller template (names matched
byte-for-byte against the templates; an unlisted-in-repo name is
harmless). Add `branches: [next, hotfixes]` so feature-branch runs no
longer wake it up. Update the reusable's header and release-flow-v4.md
to match.

Existing adopters must re-sync their release-merge.yml — the trigger
lives in the caller file, not behind @v4.

Fixes #318
@cldmv-bot cldmv-bot Bot added ! release → master v4 flow: persistent next → master release PR (carries the next feature release) release Marks a pull request as a pending release — merge to publish a new version semver: patch This release contains only backwards-compatible bug fixes type: bug Something is broken or not behaving as expected type: ci Changes to CI workflows, actions, or build pipelines type: config Changes to repository or project configuration files type: documentation Relates to docs, README updates, guides, or inline code comments labels Sep 28, 2026
@cldmv-bot
cldmv-bot Bot merged commit 3ee436f into master Sep 28, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

! release → master v4 flow: persistent next → master release PR (carries the next feature release) release Marks a pull request as a pending release — merge to publish a new version semver: patch This release contains only backwards-compatible bug fixes type: bug Something is broken or not behaving as expected type: ci Changes to CI workflows, actions, or build pipelines type: config Changes to repository or project configuration files type: documentation Relates to docs, README updates, guides, or inline code comments

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant