Conversation
1efb89d to
a102015
Compare
|
Updated this base-red fix to keep every gate green on its own tree:
Local validation on this tree: api-typecheck OK (289 within baseline), open-sse-typecheck OK (0), file-size OK, docs-sync/docs-counts/changelog-integrity OK, pack-policy OK, mutation-test-coverage OK, and the GLM + stream/SSE suites (153 tests) pass. #12893 carries the same commits as cherry-picks so its CI can go green in parallel. |
214cd4e to
e9dde45
Compare
…fact policy (base-red) diegosouzapw#12870 added @omniroute/opencode-plugin-v2 to the npm pack artifact but did not register its prefix in PACK_ARTIFACT_ROOT_ALLOWED_PATH_PREFIXES, so the pack-policy gate fails on the release tip for every open PR.
dacb1c3 to
38274c1
Compare
|
Same treatment: merged the current tip and re-synced the migration count (171→172) so CI runs on a fresh tree. Remaining red on the tip (volcengine |
|
Good catch on the missing allowlist entry — the pack-policy gap was real. It ended up landing Triage note: this is the review recommendation — the close itself happens only after the maintainer's per-PR sign-off (and, where a superseding PR is named, after it has landed). Nothing is being closed by this comment. |
|
Closing as already covered — thanks for confirming the gap was real and for landing it via the #12959 maintenance sweep (same allowlist line, plus the fresher doc counts). Nothing left to carry here. |
Summary (scope updated)
The release wave around #12870 added
@omniroute/opencode-plugin-v2/*to the npm pack artifact but never registered its prefix inPACK_ARTIFACT_ROOT_ALLOWED_PATH_PREFIXES, so the pack-policy gate fails on the release tip for every open PR. This adds the one-line prefix entry alongside the existing v1@omniroute/opencode-plugin/.History
This PR originally carried the full set of release-tip base-reds (stream highWaterMark restoration, chatCore union narrowing, doc count drift). The maintainers have since landed equivalents themselves — #12963 (pin the ok variant), #12970 (sync migration/strategy counts), and the non-streaming-leg restore wave — so those commits are dropped from this branch and all that remains is the still-unfixed pack policy entry.
Validation
validate-pack-artifact.ts --policy-only→ ✅ pass (fails on the release tip).