You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/release-notes/6.9-release-notes.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -114,6 +114,16 @@ The Notifications API has been improved (with `onlyUnread`, `limit`, and `offset
114
114
115
115
This release contains important security updates such as an upgrade to Payara (#11827) and how CORS is handled (#11745). If you are not receiving security notices, please sign up by following [the steps](https://guides.dataverse.org/en/latest/installation/config.html#ongoing-security-of-your-installation) in the guides.
116
116
117
+
## Backward Incompatible Changes
118
+
119
+
Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/latest/api/changelog.html) for a list of backward-incompatible API changes.
120
+
121
+
- CORS is no longer enabled by default. See the upgrade instructions for details as well as #11745.
122
+
- See the "Database Settings Cleanup" section below. In the past, the settings API would accept any key and value. This is no longer the case because validation has been added. Also the way to set per-format size limits for tabular ingest has changed. JSON input is now used. See #11639 and #11654.
123
+
- The Update Collection Input Levels API endpoint no longer deletes the custom input levels previously modified for the given collection. In order to update a previously modified custom input level, it must be included in the JSON provided to the api. See [the guides](https://guides.dataverse.org/en/6.9/api/native-api.html#update-collection-input-levels), #11387, and #11748.
124
+
- For `/api/admin/dataverse/{dataverse-alias}/storageDriver` and `/api/datasets/{identifier}/storageDriver` the driver name is no longer returned in data.message. Instead, it is returned as data.name (along with other information about the storageDriver). See [the guides](https://guides.dataverse.org/en/6.9/api/native-api.html#configure-a-dataset-to-store-all-new-files-in-a-specific-file-store), #11695, and #11664.
125
+
- The POST /api/admin/makeDataCount/{id}/updateCitationsForDataset processing is now asynchronous and the response no longer includes the number of citations. The response can be OK if the request is queued or 503 if the queue is full (default queue size is 1000). See #11777 and #11781.
126
+
117
127
## Developer Updates
118
128
119
129
- The ExportDataProvider framework in the dataverse-spi package has been extended, adding some extra options for developers of metadata exporter plugins. See [the guides](https://guides.dataverse.org/en/6.9/developers/metadataexport.html#building-an-exporter)#11766, and #11767.
@@ -208,16 +218,6 @@ The following database settings were added to the official list within the code
208
218
-`WorkflowServiceBean.WorkflowId:PrePublishDataset` - now `:PrePublishDatasetWorkflowId`
209
219
-`WorkflowServiceBean.WorkflowId:PostPublishDataset` - now `:PostPublishDatasetWorkflowId`
210
220
211
-
## Backward Incompatible Changes
212
-
213
-
Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/latest/api/changelog.html) for a list of backward-incompatible API changes.
214
-
215
-
- CORS is no longer enabled by default. See the upgrade instructions for details as well as #11745.
216
-
- See the "Database Settings Cleanup" section above. In the past, the settings API would accept any key and value. This is no longer the case because validation has been added. Also the way to set per-format size limits for tabular ingest has changed. JSON input is now used. See #11639 and #11654.
217
-
- The Update Collection Input Levels API endpoint no longer deletes the custom input levels previously modified for the given collection. In order to update a previously modified custom input level, it must be included in the JSON provided to the api. See [the guides](https://guides.dataverse.org/en/6.9/api/native-api.html#update-collection-input-levels), #11387, and #11748.
218
-
- For `/api/admin/dataverse/{dataverse-alias}/storageDriver` and `/api/datasets/{identifier}/storageDriver` the driver name is no longer returned in data.message. Instead, it is returned as data.name (along with other information about the storageDriver). See [the guides](https://guides.dataverse.org/en/6.9/api/native-api.html#configure-a-dataset-to-store-all-new-files-in-a-specific-file-store), #11695, and #11664.
219
-
- The POST /api/admin/makeDataCount/{id}/updateCitationsForDataset processing is now asynchronous and the response no longer includes the number of citations. The response can be OK if the request is queued or 503 if the queue is full (default queue size is 1000). See #11777 and #11781.
220
-
221
221
## Complete List of Changes
222
222
223
223
For the complete list of code changes in this release, see the [6.9 milestone](https://github.com/IQSS/dataverse/issues?q=milestone%3A6.9+is%3Aclosed) in GitHub.
0 commit comments