Skip to content

[S4] Keep pinned-submodule builds free of stale outputs #141

Open

Description

Problem

Extensions consume this repository only as a pinned Git submodule. That pins both runtimes' sources, but ignored TypeScript outputs can survive a pin change: tsc does not remove JavaScript or declarations for deleted sources.

Scope

  1. Clean shared TypeScript dist before compilation.
  2. Add one regression to the existing TypeScript suite that proves stale JavaScript/declarations are removed and the current entrypoint is built.
  3. Keep short build guidance: release CI uses a fresh checkout at the recorded gitlink, rebuilds TypeScript, and installs Python from the same submodule before packaging.

Acceptance

  • The regression fails with the original tsc-only build and passes with cleanup.
  • Existing TypeScript build/tests/lint pass with the pinned Node version.
  • No runtime API, tool behavior, dependency-version, or lockfile changes.

This replaces the earlier paired-artifact/provenance proposal. No input allowlist, snapshot/fingerprint manifest, build/verify CLI, or separate Python-wheel pipeline is needed. Consumer pipeline enforcement and compatibility tests remain extension-owned.

Implementation: #143.

Activity

  1. changed the title [-][S4] Make source builds reproducible and add pinned consumer canaries[/-] [+][S4] Keep pinned-submodule builds free of stale outputs[/+] on Nov 17, 2026
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

    debtCode Cleanup, Refactorings and Repo health. Not feature relatedtriage-needed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions