-1
We started using API versioning specifically to be able to introduce
breaking changes. If we disallow this, the whole versioning will become
even more pointless.
What concerns you is the one of the downsides of feature hiding that I was
talking about for a long time, and nobody seemed to
So, as you know, I think that a breaking change like this is really bad for
our users, no matter how loudly we declare it or when we do it. Version
negotiation in the REST API doesn't give us license to do this. I also
think most users should not need to know the version number at all, should
be
Hi all!
Today we landed a patch [1] that switches (starting with API version
1.11) node creation API to default to ENROLL node state instead of
AVAILABLE. Nothing to worry about right now: we don't default to this
API version (yet?) in our clients. But read on to figure out how not to
get
