Repository navigation
Vendor the @intx leaf packages the re-pin compiles against at a8bc06ae - #455
Merged
TheGreatAxios merged 1 commit intoAug 29, 2026
Merged
Conversation
Re-pinning any vendored @intX tree to upstream origin/main (a8bc06ae, 2026-08-27) needs the newer type surface of the packages it imports, and npm is still 0.3.0. Vendor those leaves at the same commit so no vendored tree ever mixes pins: types, agent, inference, mime, mail-memory, and the new mailbox package (not published at all). Root overrides now point each vendored name at workspace:* so the published @intx/harness, hub-agent, tool-packaging, authz, ... resolve their own @intx/* dependencies onto the vendored copies instead of a second npm copy; unchanged names stay pinned to 0.3.0. @types/ssri joins the root catalog the way upstream carries it. Two ledgered edits: inference builds the Gemini upload body as new Uint8Array(bytes) because TS 6's lib.dom BodyInit rejects Uint8Array<ArrayBufferLike> in the DOM-lib packages that compile this source; the still-pinned workflow-host's supervisor-backed transport returns the expunged uids from its expunge stub to match the re-pinned types (bridging edit, gone with that tree's re-pin).
TheGreatAxios
changed the title
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.
Re-pin wave 2, PR 1/7. Target pin: upstream faremeter/interchange
a8bc06ae(origin/main, 2026-08-27); npm@intx/*is still 0.3.0.Changed
@intx/types,agent,inference,mime,mail-memoryand the newmailboxpackage ata8bc06ae(upstream*.test.tsstripped; exports →./src, nointx-srccondition).overrides: vendored names →workspace:*so published@intx/harness/hub-agent/tool-packaging/… resolve the vendored copies instead of a second npm copy; unchanged names stay0.3.0.@types/ssrijoins the root catalog as upstream carries it.workspace:*.Kept (deltas, ledgered)
inference/providers/google-genai-files.ts:body: new Uint8Array(bytes)— TS 6 lib.domBodyInitrejectsUint8Array<ArrayBufferLike>; upstream compiles ESNext-only under TS 5.9.workflow-host(expungestub return type) — gone in PR 6.Why these six: they are the only npm-consumed packages whose source drifted between v0.3.0 and
a8bc06ae(authz/crypto/hub-common/log/pack-transport/storage-isogit/tool-packaging/inference-catalog are byte-identical and stay on npm).Not done: nothing deferred.