Skip to content

Hold the not-found reason copy to the per-SKU enum, release v0.48.1 - #49

Merged
kev1n merged 1 commit into
mainfrom
not-found-reason-per-sku
Sep 19, 2026
Merged

kev1n merged 1 commit into
mainfrom
not-found-reason-per-sku

Conversation

@kev1n

@kev1n kev1n commented Sep 19, 2026

Copy link
Copy Markdown
Member

The v0.48.0 release gate failed before publishing: not-found-reason.test.ts expected every operation to publish [not_found, suspended], but since anyapi#1202 the gateway publishes per SKU only the reasons that SKU's sources can answer with (377 operations [not_found], 2 [not_found, suspended]).

Both language tests now require each published enum to be an in-order subset of NOT_FOUND_REASONS, and every runtime word to be published somewhere. Version surfaces bumped to 0.48.1; tag v0.48.0 stays unpublished.

Gates: pnpm check green; pyright 0 errors, mypy clean, pytest 517 passed.

🤖 Generated with Claude Code

…hes, and release v0.48.1

The gateway publishes on each SKU only the reasons its own sources can answer
with (anyapi#1202), so 377 operations declare [not_found] and 2 declare
[not_found, suspended]. The vocabulary test demanded the full list on every
operation, which failed the v0.48.0 release gate before anything published.
Each enum must now be an in-order subset of NOT_FOUND_REASONS, and every
runtime word must be published somewhere.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@kev1n
kev1n merged commit 919f500 into main Sep 19, 2026
4 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