Skip to content

v5.0.0

  • v5.0.0
  • 578e5f7
  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
  • Choose a tag to compare

  • v5.0.0
  • 578e5f7
  • Choose a tag to compare

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
@lloyal-research lloyal-research tagged this 16 Aug 04:49
The wire-format change in #94 renamed fields on PUBLIC exported types and was
merged without bumps, so the published 4.0.0/0.2.0 do not carry it. Both renames
are breaking for a TypeScript consumer, not merely cosmetic:

  agents          AbilityManifest.appProtocolVersion → abilityProtocolVersion
  channel-verify  CatalogVersion.appProtocolVersion  → abilityProtocolVersion
                  CHANNEL_CATALOG_URL → /v1/abilities/catalog.json

So agents and rig take majors and channel-verify a 0.x minor, which is how a
0.x signals breaking. Two majors in one day is heavy, and the alternative —
shipping a renamed public field under a patch — is worse: it would break
consumers silently at a version range that promised not to.

The three abilities stay at 2.0.0. They are channel-only, never published to
npm and not yet signed into the catalog at that version, so 2.0.0 is still
unclaimed; only their peer ranges move to ^5.0.0.

Lockfile reconciled via `npm version` per workspace and verified in sync — a
stale lockfile fails `npm ci` in CI even though release.yml uses `npm install`.

64 test files, 572 passed / 2 skipped.
Assets 2
Loading