Closed jdoklovic closed 5 years ago
@jdoklovic I read the article a couple weeks ago. But the API specification is not changed yet :thinking:
Could you provide any insight about if it will change (removal of deprecated endpoints and addition of new endpoints) after 12 April 2019 all at once or will there be addition of new ones and some kind of deprecation tag for the deprecated ones in the specification first and then removal after 12 April 2019?
I believe it's going to be an all at once deal. I'll check with the bitbucket team and get back with you
Not much will change between now and April. Everything should already be in place to allow clients to move away from usernames today. The only thing that happens in April is that the username field will disappear from all responses and URLs.
If you have any specific concerns or questions around how to effectively use the API without usernames, please let me know.
Thanks for the information. :+1:
I'll add a warning message in the library that is logged at startup.
v1.7.0
released with Bitbucket Cloud API Change Notice...
:tada:
Atlassian is changing how APIs deal with usernames.
see: https://developer.atlassian.com/cloud/bitbucket/bitbucket-api-changes-gdpr/