hi! compatibility is verified against latest versi...
# general
d
hi! compatibility is verified against latest versions with tag is there a mechanism, to verify against • latest n versions with tag ◦ or • versions having tag within last n months
m
What’s your use case Dmitry?
Recording releases is probably the best way of managing this. You
release
a version of a consumer and a provider can verify all released versions. When a version is no longer relevant, you un-release it
I’d be concerned about “last n” or time based, because it is not very specific and could result in more tests running that aren’t relevant, or false positives because we’ve overnight stopped caring about an important version
d
we have ios bundle - bunch of JS statics our client gets bundles from all suppliers and makes big app sends to Appstore all this hassle is very time consuming and could last months so how can we track, that bundle we shipped some time ago is compatible
last n is more scary
so, lets assume - we must support our stuff for 1/2 year
with just checkin
live
its not enough
When a version is no longer relevant, you un-release it
looks like i need google something 🙂
looks like this ?
record-undeployment --pacticipant my-retired-service --environment test
Copy code
record-support-ended --pacticipant foo-mobile-app --version 6897aa95e --environment production
much wow
still this is some manual thing
like after some time i need to find that
--version 6897aa95e
or then there is a need in some webhook/api, which would fetch something and un-release based on something