release: v1.14.19 — fix release pipeline for real (npm 10 --ignore-scripts bug) - #308
Merged
Merged
Conversation
📦 Built Plugin ArtifactBranch: Option A — Install from npm PR tag (recommended)opencode plugin opencode-acp@pr-308 --globalEach push to this PR publishes a new version under the Option B — Install from GitHubopencode plugin "github:ranxianglei/opencode-acp#2026-08-15_release-v1.14.19" --globalOption C — Download artifact
tar xzf opencode-acp-pr308.tgz
cp -r package/dist ~/.cache/opencode/packages/opencode-acp@latest/node_modules/opencode-acp/dist
This comment is automatically updated on each push. |
|
✅ Published opencode plugin opencode-acp@latest --global |
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
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.
Problem
v1.14.18 (#306) was merged but never published —
release.ymlfailed at the exact sameverify-package.mjsstep as v1.14.17. The v1.14.18 fix (npm pack --ignore-scripts) turned out to be insufficient: the CI runner uses Node 22 (npm 10.9.x), and npm 10 runs thepreparelifecycle hook duringnpm packeven when--ignore-scriptsis passed. The flag works on npm 11 (local Node 25), which is why local verification passed but CI failed.When prepare runs, tsup writes
CLI Building entry: index.tsto stdout, breakingJSON.parseinverify-package.mjs.Two consecutive versions (1.14.17, 1.14.18) failed to publish because of this.
Fix
Redirect the
preparebuild's stdout to stderr:"prepare": "npm run build 1>&2"inpackage.json.--ignore-scriptsworksnpm pack --dry-run --jsonreturns valid JSON (173 tarball entries) both with and without--ignore-scripts--ignore-scriptsflag from v1.14.18 is kept (harmless on npm 10, skips redundant rebuild on npm 11)npm install github:...#branchpath unaffected — prepare still runs and still buildsdist/Verification
npm run build: 391.59 KB ✓node scripts/verify-package.mjs: passed, 173 tarball entries ✓ (npm 10.9.9 + npm 11.12.1)./scripts/ci/check-pr.sh: all checks passed ✓After merge
CI will auto-publish v1.14.19 to npm
latest(this also finally ships everything from the unpublished 1.14.17 + 1.14.18). Then PR #307 (promote stable) needs retargeting from v1.14.18 → v1.14.19.