Coldkeep v1.13.2 — Engine Error Taxonomy Baseline #91
franchoy
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Coldkeep v1.13.2 — Engine Error Taxonomy Baseline
Coldkeep v1.13.2 establishes the first engine/catalog error taxonomy baseline for the v1.13 release train.
This release introduces narrow, code-backed taxonomy primitives for the stable surfaces that exist today, documents the broader taxonomy language, and protects public CLI behavior from accidental taxonomy leakage.
Highlights
Added narrow engine unsupported classification:
engine.IsUnsupported(err error) boolerrors.Is(err, engine.ErrNotImplemented)Added narrow catalog deferred classification:
catalog.IsDeferred(err error) boolerrors.Is(err, catalog.ErrNotImplemented)Preserved engine/catalog sentinel separation:
Added focused boundary tests for:
Added v1.13.2 release documentation:
Public behavior
No public behavior changes.
This release does not change:
Explicit non-goals
This release does not implement:
Validation
The v1.13.2 release gate passed and was marked ready before PR review.
Validation included:
mainafter mergePRE_RELEASE_CHECKLIST.mdProfile Ago test -count=1 ./...go test -race -count=1 ./...go vet ./...golangci-lint run ./...Handoff
v1.13.3 should focus on read-side contract cleanup for:
That work should use the v1.13.2 taxonomy baseline while continuing to preserve public CLI behavior, JSON output, exit codes, and routing unless explicitly scoped otherwise.
This discussion was created from the release Coldkeep v1.13.2 — Engine Error Taxonomy Baseline.
All reactions