fix(ci): remove gutted plugin-sdk paths + sync extension allowlists#2397
Merged
alexey-pelykh merged 1 commit intomainfrom Apr 18, 2026
Merged
fix(ci): remove gutted plugin-sdk paths + sync extension allowlists#2397alexey-pelykh merged 1 commit intomainfrom
alexey-pelykh merged 1 commit intomainfrom
Conversation
B8 DIFF-SYNC (#2395) introduced two publish-next regressions: 1. scripts/release-check.ts required plugin-sdk build outputs for 5 gutted providers (google-gemini-cli-auth, memory-core, memory-lancedb, minimax-portal-auth, qwen-portal-auth). Fork doesn't build these — the Middleware Boundary excludes LLM provider auth and memory subsystems. Remove 10 required-path entries (.js + .d.ts each). 2. 6 extension package.json files (googlechat, matrix, msteams, nostr, tlon, zalouser) had stale rootDependencyMirrorAllowlist entries pointing to root deps that ARE present. The validator enforces allowlist == missing-in-root; fork's root has the mirrors so allowlist must be empty. Sync all 6 extensions to match actual missing-in-root (which is [] for all). Test: release-check.test.ts 9/9 pass.
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.
Fix B8 publish-next regressions (round 2)
Two post-merge regressions from B8 DIFF-SYNC (#2395):
1. Required plugin-sdk paths for gutted providers
Upstream v2026.3.12 added 5 new plugin-sdk required-path groups to `scripts/release-check.ts`:
Fork has gutted all 5 subsystems (LLM provider auth + memory — outside Middleware Boundary). The fork's build doesn't produce these dist/ outputs, so the `release-check` "missing files in npm pack" validation fails.
Removed 10 path entries (5 `.js` + 5 `.d.ts`).
2. Stale rootDependencyMirrorAllowlist drift
6 extension `package.json` files had allowlist entries for deps that ARE present in root `package.json`:
Validator enforces `allowlist == missing-in-root`. Fork root mirrors these, so allowlist must be empty for all 6.
Reset all 6 allowlists to `[]` to match actual missing-in-root (all empty).
Test: `pnpm vitest run test/release-check.test.ts` 9/9 pass.
🤖 Generated with Claude Code