Skip to content

fix(release): stop invoking postinstall/version scripts removed by rc.39 - #120

Merged
elliotBraem merged 1 commit into
mainfrom
fix/release-workflow-postinstall
Nov 5, 2026
Merged

elliotBraem merged 1 commit into
mainfrom
fix/release-workflow-postinstall

Conversation

@elliotBraem

Copy link
Copy Markdown
Contributor

Problem

The Release (Version Packages) workflow fails on main since #119 — see run 42084938527:

Error: ERR_PNPM_NO_SCRIPT
  × Missing script: postinstall

The everything-dev 2.0.0-rc.39 upgrade removed the postinstall, version, changeset, and release scripts from package.json per the framework's child-template convention (upstream #572 removes the changesets glue from children). The workflow still invoked two of them.

Fix (workflow-only)

  • Remove the Run postinstall step — nothing downstream in this workflow needs generated types: changeset version is pure file ops, and the GH-release step is jq/sed.
  • version: pnpm run version → version: pnpm exec changeset version — the changesets action would have hit Missing script: version next (there are 5 pending changesets on main); this calls the @changesets/cli devDependency binary directly.

No package.json changes: keeping it aligned with the rc.39 template means the next bos upgrade won't clobber this.

Verification

  • CI green on this PR
  • After merge: the Release workflow auto-fires on CI success on main and should create/update the chore: version packages PR (which also un-stales the currently CONFLICTING chore: version packages #88)

PR #119 (everything-dev 2.0.0-rc.39) removed the postinstall, version,
changeset, and release scripts from package.json per the framework's
child-template convention (#572 removes changesets glue from children).
The Release workflow still called two of them:

- 'Run postinstall' failed with ERR_PNPM_NO_SCRIPT (run 42084938527),
  so the drop removes the step — nothing downstream needs generated
  types: 'changeset version' is file ops and the GH-release step is
  jq/sed.
- The changesets action's 'version: pnpm run version' would fail the
  same way on the next run (5 pending changesets on main), so it now
  invokes the devDependency binary directly via 'pnpm exec changeset
  version'.

No package.json changes: keeping it aligned with the rc.39 template
means the next bos upgrade won't clobber the fix.
@elliotBraem
elliotBraem merged commit f4de2b4 into main Nov 5, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant