backward incompatible API changes coming in Dataverse 6.12

[Philip Durbin]

Hi! We just merged https://github.com/IQSS/dataverse/pull/12097 and it has some backward incompatible changes when interacting with the Dataverse API.

We always list backward incompatibilities in the API changelog at release time but I thought I'd give an extra heads up and invite you to test on https://beta.dataverse.org where the change has already been deployed.

To give you an example, we've cleaned up how "message" is returned.

## old, v6.11, weirdly double, from https://demo.dataverse.org

{
  "status": "OK",
  "message": {
    "message": "Update successful"
  },
  "data": {

## new, v6.12 (pre-release), cleaner, from https://beta.dataverse.org

{
  "status": "OK",
  "message": "Update successful",
  "data": {

That was from this API endpoint, specifically: https://guides.dataverse.org/en/6.11/api/native-api.html#change-collection-attributes

This is just an example and this email is already long enough. For the gory details, please click "files changed" on the pull request above and check out the release note snippet, other docs, and changes to tests. You can also preview the API changelog here: https://preview.guides.gdcc.io/en/develop/api/changelog.html

Thanks,

Phil

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin