chore: release package

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@adcp/sdk@11.2.0

Minor Changes

• 57f90ed: Add a lean, zero-dependency ./enums export. import { EventTypeValues } from '@adcp/sdk/enums' (and the other AdCP enum value arrays) now resolves to a zod-free entry point, so bundlers no longer pull the full ./types barrel and zod (~1.84 MB) just to read an enum. Useful for zod-free consumers such as browser bundles. Re-exports the existing types/enums.generated (named unions) and types/inline-enums.generated (per-field unions) modules; no change to ./types.

Patch Changes

• 3d90d17: fix(runtime): list_accounts projects CursorPage into the pagination block instead of top-level next_cursor

  Both 3.0 and 3.1 list-accounts-response model pagination via pagination: { has_more, cursor?, total_count? } referencing core/pagination-response.json. The prior projector emitted next_cursor at the top level — schema-invisible under additionalProperties: true, but every adopter silently failed the pagination_integrity_list_accounts storyboard's field_value pagination.has_more: true + field_present pagination.cursor assertions regardless of accounts.list output. Fixes comply_test_controller(scenario=seed_account) returns UNKNOWN_SCENARIO — blocks pagination_integrity_list_accounts for every implementer adcp#5723.

• 4bb51b5: Stop schema syncs from clobbering checked-in protocol skills and the registry spec.

  sync-schemas wrote two non-version-scoped, checked-in files on every run: the protocol skills (skills/adcp-*) and schemas/registry/registry.yaml. A side-bundle sync (sync-schemas -- 3.0.12, sync-schemas:3.1-beta) therefore overwrote the primary pin's skills with an older version's content, and even the primary sync overwrote the registry spec — which is actually owned by generate-registry-types --sync from a different upstream. Both left a spurious diff in the working tree after any sync.

  The skill sync now runs only when syncing the primary pin, the latest/ cache pointer is likewise only repointed for the primary pin (a side-bundle sync no longer silently makes the SDK validate against an older version by default), and the registry spec is no longer written by sync-schemas at all (its owner is generate-registry-types --sync). This removes the fragile restoreFromHead/RESTORE_PATHS workaround in the beta sync script.

[aao-ipr-bot]

Automated Changesets release PR — approve. Version bump is calculated by the changesets action from consumed changesets, not edited by hand, which is exactly how @adcp/sdk versioning is supposed to flow.

Things I checked

• Version math. Two changesets consumed — lean-enums-export (minor) + fix-list-accounts-pagination-shape (patch). Combined → minor. 11.1.0 → 11.2.0. No skipped version.
• package.json bump is changeset-driven, not manual. package.json:3 11.1.0 → 11.2.0 matches the minor calculation from the deleted changesets. Not a hand edit — MUST FIX #6 does not apply.
• Lockstep across the workspace. package-lock.json root + workspace entries, packages/client-shim/package.json:109 dep ^11.1.0 → ^11.2.0, and src/lib/version.ts all move together. No drift.
• Library vs schema version separation held. src/lib/version.ts:71 library: '11.2.0' bumps; adcp: '3.1.2' unchanged. Independent axes, correct.
• CHANGELOG generated, not authored. CHANGELOG.md gains the 11.2.0 section with both entries; changeset files deleted. Standard release consumption — no new changeset required on a release PR.

No library behavior changed here beyond the LIBRARY_VERSION constant and the generatedAt timestamp. Nothing on the wire.

LGTM.

[aao-ipr-bot]

⚠️ Argus review could not complete (no verdict or review body was produced). A human reviewer should take this PR. View workflow run

[aao-ipr-bot]

⚠️ Argus review could not complete (no verdict or review body was produced). A human reviewer should take this PR. View workflow run