Skip to content

deprecate: manifest-based provisioner — IMF registry is the path - #49

Merged
ronaldtse merged 1 commit into
mainfrom
deprecate/manifest-provisioner
Aug 27, 2026
Merged

deprecate: manifest-based provisioner — IMF registry is the path#49
ronaldtse merged 1 commit into
mainfrom
deprecate/manifest-provisioner

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

The manifest-based provisioner resolves version-to-URL through a
manifest that has never been published anywhere — the default CDN URL
404s (and contains a doubled path segment), and the
@interscript/models package it names was deprecated before release.
The IMF registry (imf, GitHub Releases + sha256 sidecar) is the
canonical path as of 3.2.0.

  • Both resolution failure paths now tell the user exactly that, with
    the imf.resolve incantation (tests cover no-manifest-published and
    no-matching-entry)
  • Public manifest APIs carry @deprecated annotations
  • Corrected the stale "source of truth" docblock; inline-manifest and
    explicit-URL behavior unchanged
  • Non-breaking: 247 tests green, tsc clean, prettier clean.
    Version 3.3.0.

No manifest has ever been published (the @interscript/models package
was never released; the CDN manifest.json URL 404s — with a doubled
path segment in the default URL). Both failure paths now direct users
to imf.resolve (GitHub Releases index, sha256-verified). Public
manifest APIs get @deprecated annotations; explicit-URL and
inline-manifest (test/air-gapped) use is unchanged.
@ronaldtse
ronaldtse merged commit 04441c6 into main Aug 27, 2026
8 checks passed
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