can I get a sanity check here? I’m thinking about API version retirement. Let’s say I (provider) am supporting V1 and V2 of my API and I want to retire (delete) V1. My rough plan would then be: 1. get all consumers to stop publishing contracts for V1 (of course that their app should equally stop using V1, otherwise none of this works) 2. all consumers would, of course, be using V2 at this stage 3. because these new without-V1 contracts are being verified, they can roll out (can-i-deploy would be happy still) 4. consumers rollout 5. in a feature branch my provider stops verifying V1 API contracts, consequently all V1 code is removed 6. in theory, because all consumers have no-V1 versions rolled out (and recorder) can-i-deploy is also happy for my provider 7. provider-without-V1 rolls out (voila!)

Sounds about right to me!