Skip to content

build: advance the shared TypeScript checker to Bun 1.4.4 #61

Closed

Description

@igorls

The operator explicitly selected Bun 1.4.4 on 2026-10-22 for ongoing Hyperion 4.5 engineering. Advance the shared TypeScript checker baseline and existing repository pins together, preserving historical run evidence at its original versions.

Update the accepted toolchain policy and current engineering guidance, then the History API, SDK and existing TypeScript plugin pins/CI where applicable. Keep TypeScript 7.0.2 unless the verified embedded checker requires an explicitly documented compiler decision; verify process.versions.typescript rather than assuming it. Preserve scripts-enabled npm ci with committed npm locks, native TypeScript artifact emission and Node 22/24 validation. Do not add empty gates to Rust or JavaScript-only catalog repositories.

Use isolated worktrees and immutable verified Bun 1.4.4 artifacts for checks. Record repository-specific validation and open scoped implementation PRs without automatic merge or deployment. The History API toolchain branch may build on the open installed native-profile pin #273 so the active worker qualification can use the new baseline consistently.

Track the upstream Undici work separately: the operator's oven-sh/bun#27338 is included in the open consolidation oven-sh/bun#46528. Neither bundling nor the 1.4.4 toolchain bump establishes that the fix is in a released binary or qualifies Hyperion's Bun runtime. Keep the actual transport/storage/worker runtime gates in History API #197 and the profiling program #28.

Release coordination: #24.

Activity

  1. igorls commented on Oct 22, 2026

    @igorls
    MemberAuthor

    The coordinated Bun 1.4.4 checker PRs are open and all CI checks pass on their recorded heads:

    The official Bun 1.4.4 executable was verified to embed TypeScript 7.0.2. Native Node 22/24 builds and tests passed: HAPI 1,075 tests per runtime, SDK 68 plus packed consumers, and Wire 959 plus packed consumers, fixture/capture guards and existing CI conformance gates. Dependency locks and historical 1.4.3 records remain unchanged.

    AtomicAssets at 13258c7 is a documentation-only scaffold without a TypeScript package or Bun pin, so no empty checker gate was added. Tools #62 retains the exact released-runtime Elasticsearch observation: Bun 1.4.4 still fails the locked client's info/close calls. Production runtime acceptance remains tracked separately in History API #197 and Tools #28. No PR was merged or deployed automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions