Skip to content

Allow the @intx 0.3.0 line - #8

Merged
TheGreatAxios merged 1 commit into
mainfrom
bump-intx-types-0.3.0
Sep 8, 2026
Merged

Allow the @intx 0.3.0 line#8
TheGreatAxios merged 1 commit into
mainfrom
bump-intx-types-0.3.0

Conversation

@TheGreatAxios

@TheGreatAxios TheGreatAxios commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

What

Widens the @intx peer ranges from ^0.2.2 to ^0.3.0 (@intx/types, @intx/hub-api), and bumps the dev dependencies to match (adding @intx/authz).

Rebased onto main after #5 and #7, which introduced the @intx/hub-api and @intx/authz dependencies.

Why

A host on the current Interchange line cannot satisfy ^0.2.2 and has to carry a package-manager override to install this package at all. That override is invisible at review time and easy to get wrong, so it is better fixed here.

Why it is safe

Every symbol this package imports from @intx is unchanged in 0.3.0:

Package Imported
@intx/hub-api idResource, RequireGrant, TenantEnv, createRequireGrant
@intx/authz createInMemoryGrantStore (tests only)
@intx/types isAllowedMimeType
  • dist/middleware/grant.d.ts is byte-identical between 0.2.2 and 0.3.0 — that file is idResource, RequireGrant and createRequireGrant.
  • TenantEnv is unchanged.
  • @intx/authz's index only gains exports in 0.3.0 (authorizeAction, AuthorizeDecision, toolConsumer, EvalOptions); nothing is removed.
  • ATTACHMENT_ALLOWLIST still carries the same 22 media types, so the type isAllowedMimeType narrows to is the same.

Verification

On the 0.3.0 line:

  • bun run typecheck (tsc --noEmit) — clean
  • bun run pretest (dep-guard) — clean
  • bun test src/content-store.test.ts src/web-site.test.ts src/migrations.test.ts17 pass / 41 fail, which is identical to main unmodified. The failures are the test harness refusing to run without a live allowlisted Postgres, not a regression. The full Postgres-backed suite was not run here; nothing in this change touches a query path.

Context

Found while mounting an Interchange hub alongside @corbits/artifacts on a shared database. The package works fine on 0.3.0 — the ranges were the only thing in the way.

The peer ranges pinned ^0.2.2, so a host on the current Interchange line cannot
satisfy them without a package-manager override.

Every symbol this package imports from @intX is unchanged in 0.3.0:

  @intx/hub-api   idResource, RequireGrant, TenantEnv, createRequireGrant
  @intx/authz     createInMemoryGrantStore (tests)
  @intx/types     isAllowedMimeType

dist/middleware/grant.d.ts is byte-identical between 0.2.2 and 0.3.0, TenantEnv
is unchanged, and @intx/authz's index only gains exports — authorizeAction,
toolConsumer, EvalOptions — none removed. ATTACHMENT_ALLOWLIST still carries the
same 22 media types, so the type isAllowedMimeType narrows to is the same.

Verified on 0.3.0: tsc --noEmit clean, dep-guard clean. The Postgres-backed
suite is unchanged — 17 pass / 41 fail both before and after, the failures being
the harness refusing to run without a live allowlisted database.
@TheGreatAxios TheGreatAxios changed the title Allow @intx/types 0.3.0 Allow the @intx 0.3.0 line Sep 8, 2026
@TheGreatAxios
TheGreatAxios merged commit 8d4e156 into main Sep 8, 2026
1 check passed
@TheGreatAxios
TheGreatAxios deleted the bump-intx-types-0.3.0 branch September 8, 2026 17:38
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