API Versioning

Use when a ticket must change an API in a way clients might notice — renaming or removing a field, changing a type or status code, altering semantics — and the change must be made compatibly or through an explicit version with a deprecation path, never as a silent break. Invoke for "change the response shape", "rename the field", "we need v2", "deprecate the old endpoint", or when a contract test fails on purpose.

tmj-90 Updated 1 repo stars
The Overview headline and scoreboard: eight things need you, the blocked ticket that leads them, three agents on the pitch, six tickets delivered today and the

File contents

tmj-90/gaffer commit 19bef931b5

Frequently asked questions

npx get-skill add tmj-90/api-versioning