diff --git a/doc/release-notes/10156-fast-redeploy-scripts.md b/doc/release-notes/10156-fast-redeploy-scripts.md
deleted file mode 100644
index 2d53ba13ab8..00000000000
--- a/doc/release-notes/10156-fast-redeploy-scripts.md
+++ /dev/null
@@ -1,42 +0,0 @@
-## Fast Redeploy Scripts for Container-Based Development
-
-Three new shell scripts in `scripts/dev/` enable fast iterative development for Dataverse contributors working with the container-based development environment:
-
-- **`dev-start-frd.sh`**: One-time setup (full build → exploded WAR → start containers)
-- **`dev-frd.sh`**: Incremental recompile + redeploy (~12s vs. ~54s for traditional full rebuild workflow, 4.5x faster)
-- **`dev-down-frd.sh`**: Clean shutdown of dev environment
-
-This command-line workflow provides a fast feedback loop for developers who prefer CLI-based development or use lightweight editors like VS Code or Vim, complementing the existing IDE-based hot reload options (IntelliJ Ultimate, NetBeans).
-
-### New Files
-
-- **`docker-compose.override.yml`**: Increases memory limits to 8GB (from the 2GB limit set for GitHub Actions CI) for local development. Automatically used by the fast-redeploy scripts.
-
-### Key Features
-
-- No infrastructure changes (works with existing docker-compose-dev.yml)
-- Optional workflow (doesn't affect other development approaches)
-- Completes in ~12 seconds instead of ~54 seconds after code changes (4.5x faster)
-
-**Note:** Performance timings may vary depending on your hardware configuration.
-
-### Typical Workflow
-
-```bash
-# One-time setup
-./scripts/dev/dev-start-frd.sh
-
-# Make code changes...
-
-# Fast redeploy
-./scripts/dev/dev-frd.sh
-
-# Repeat as needed
-
-# When finished
-./scripts/dev/dev-down-frd.sh
-```
-
-### Documentation
-
-See the [Fast Redeploy (Command-Line)](https://guides.dataverse.org/en/latest/container/dev-usage.html#dev-fast-redeploy) section in the Container Guide for complete usage instructions and limitations.
diff --git a/doc/release-notes/10398-geospatial-block.md b/doc/release-notes/10398-geospatial-block.md
deleted file mode 100644
index 50eea141883..00000000000
--- a/doc/release-notes/10398-geospatial-block.md
+++ /dev/null
@@ -1,22 +0,0 @@
-## New Expanded Geospatial Metadata Block
-
-This release introduces a major enhancement to geospatial data support with the addition of an expanded Geospatial Metadata Block, designed to improve how researchers describe, share, and discover geospatial datasets.
-
-This new expanded metadata block aligns with the international ISO 19115 standard for describing geographic data.
-
-- Includes 22 new metadata fields to provide more detailed and standardized descriptions of geospatial data (e.g. vector, raster, mixed or multi-format geospatial collections)
-- Incorporates and extends current metadata elements (Geographic Coverage and Geographic Bounding Box)
-- Ensures backward compatibility while significantly improving metadata description capabilities.
-
-See [the guides](https://dataverse-guide--11507.org.readthedocs.build/en/11507/user/appendix.html#supported-metadata), #10398, and #11507.
-
-## Upgrade Instructions
-
-### Update geospatial metadata block in existing installation (PR #11507)
-
-.. code-block:: javascript
-  
-  curl http://localhost:8080/api/admin/datasetfield/load -H "Content-type: text/tab-separated-values" -X POST --upload-file geospatial.tsv
-  curl "http://localhost:8080/api/admin/index/solr/schema" > new.xml
-  ./dataverse/conf/solr/update-fields.sh /usr/local/solr/solr-9.8.0/server/solr/collection1/conf/schema.xml new.xml
-  curl "http://localhost:8983/solr/admin/cores?action=RELOAD&core=collection1"
diff --git a/doc/release-notes/11447-mydata-retrieve-empty-result-set.md b/doc/release-notes/11447-mydata-retrieve-empty-result-set.md
deleted file mode 100644
index 949da5780c7..00000000000
--- a/doc/release-notes/11447-mydata-retrieve-empty-result-set.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## Feature MyData API Endpoint - don't return error for empty result set
-
-**GET /api/mydata/retrieve** will now return "data" block with 0 results if the result set is empty, Also, the "success" status will be returned as 'true' and the message giving context as to the 0 results will be returned in "message" instead of "error_message".  All true errors will still return "success":false and "error_message":"Some error" with no "data" block.
diff --git a/doc/release-notes/11588-search-api-doesnt-return-image-url.md b/doc/release-notes/11588-search-api-doesnt-return-image-url.md
deleted file mode 100644
index 6d0a474281c..00000000000
--- a/doc/release-notes/11588-search-api-doesnt-return-image-url.md
+++ /dev/null
@@ -1,4 +0,0 @@
-## BUG ##
-Search API doesn't return image_url after newly created dataset is published.
-
-The Dataset thumbnail will be created automatically when a Dataset is published under the following conditions: The Dataset has no existing thumbnail; The Dataset has image files that can be converted to a thumbnail; The Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled;
diff --git a/doc/release-notes/11733-api-get-file-citation-format.md b/doc/release-notes/11733-api-get-file-citation-format.md
deleted file mode 100644
index b315e8176b8..00000000000
--- a/doc/release-notes/11733-api-get-file-citation-format.md
+++ /dev/null
@@ -1,4 +0,0 @@
-### Feature New API ###
-New API added to retrieve the DataFile Citation in a requested format. This is similar output to the API to get the Dataset Citation.
-
-SERVER_URL/api/access/datafile/{fileId}/citation/{format}
diff --git a/doc/release-notes/11912-edit-template-apis b/doc/release-notes/11912-edit-template-apis
deleted file mode 100644
index 91324f38330..00000000000
--- a/doc/release-notes/11912-edit-template-apis
+++ /dev/null
@@ -1,23 +0,0 @@
-## New Endpoint: PUT `/dataverses/{templateId}/metadata`
-
-A new endpoint has been implemented to edit the metadata and field instructions for a given template.
-
-### Functionality
-- Updates the metadata and field instructions for a template based on a json file provided.
-- You must have edit dataverse permission in the collection in order to use this endpoint.
-
-## New Endpoint: PUT `/dataverses/{templateId}/licenseTerms`
-
-A new endpoint has been implemented to edit the license or custom terms of use for a given template.
-
-### Functionality
-- Updates the license or custom terms of use for a template based on a json file provided.
-- You must have edit dataverse permission in the collection in order to use this endpoint.
-
-## New Endpoint: PUT `/dataverses/{templateId}/access`
-
-A new endpoint has been implemented to edit the terms of access for a given template.
-
-### Functionality
-- Updates the terms of access for a template based on a json file provided.
-- You must have edit dataverse permission in the collection in order to use this endpoint.
diff --git a/doc/release-notes/11920-more-ra-info.md b/doc/release-notes/11920-more-ra-info.md
deleted file mode 100644
index 7ef12e06fea..00000000000
--- a/doc/release-notes/11920-more-ra-info.md
+++ /dev/null
@@ -1 +0,0 @@
-All API endpoints that return information about role assignments (such as `/api/dataverses/$ID/assignments`) now include additional fields in their JSON responses: `assigneeName`, `roleDescription`, `definitionPointName`, `definitionPointType`, and `definitionPointGlobalId` (if available).
\ No newline at end of file
diff --git a/doc/release-notes/11998-features-in-guides.md b/doc/release-notes/11998-features-in-guides.md
deleted file mode 100644
index 1f96b99463f..00000000000
--- a/doc/release-notes/11998-features-in-guides.md
+++ /dev/null
@@ -1 +0,0 @@
-A [list of Dataverse features](https://dataverse-guide--12000.org.readthedocs.build/en/12000/admin/features.html) has been added to the guides. See #11998 and #12000.
diff --git a/doc/release-notes/12014-croissant-1.1.md b/doc/release-notes/12014-croissant-1.1.md
deleted file mode 100644
index 44c796c593d..00000000000
--- a/doc/release-notes/12014-croissant-1.1.md
+++ /dev/null
@@ -1,25 +0,0 @@
-### Croissant 1.1 (Summary Statistics)
-
-The Croissant metadata export format has been updated from version 1.0 to 1.1.
-
-Summary statistics (mean, min, max, etc.) are now included for tabular files that were successfully ingested.
-
-You can download an example Croissant file from the [Supported Metadata Export Formats](https://dataverse-guide--12214.org.readthedocs.build/en/12214/user/dataset-management.html#supported-metadata-export-formats) section of the guides.
-
-Minor backward-incompatible changes were made, which are noted below.
-
-See #12014 and #12214
-
-## Backward Incompatible Changes
-
-Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/latest/api/changelog.html) for a list of backward-incompatible API changes.
-
-Minor changes in the `croissant` format are noted in the [API changelog](https://dataverse-guide--12214.org.readthedocs.build/en/12214/api/changelog.html).
-
-## Upgrade Instructions
-
-1. Re-export metadata export formats
-
-   We re-export because the Croissant format was updated.
-
-   `curl http://localhost:8080/api/admin/metadata/reExportAll`
diff --git a/doc/release-notes/12070-datacite-getmetadata.md b/doc/release-notes/12070-datacite-getmetadata.md
deleted file mode 100644
index dcef698e3e5..00000000000
--- a/doc/release-notes/12070-datacite-getmetadata.md
+++ /dev/null
@@ -1,11 +0,0 @@
-Incremental improvements have been made to the process of registering dataset metadata with DataCite. If your instance is using DataCite, please make sure you have a valid DataCite REST API url configured, since it is now required.
-
-The JVM option(s) in question are `dataverse.pid.*.datacite.rest-api-url` if the recommended, new-style pid configuration is used, or `doi.dataciterestapiurlstring` if the legacy settings are in place. In the latter case however, this may be a good occasion to switch to the new configuration setup.
-
-For instances using registered DataCite authorities in production the url should be:
-
-```<jvm-options>-Ddataverse.pid.<providername>.datacite.rest-api-url=https://api.datacite.org</jvm-options>```
-
-Or, for test and development instances:
-
-```<jvm-options>-Ddataverse.pid.<providername>.datacite.rest-api-url=https://api.test.datacite.org</jvm-options>```
\ No newline at end of file
diff --git a/doc/release-notes/12112-get-default-contributor-role.md b/doc/release-notes/12112-get-default-contributor-role.md
deleted file mode 100644
index 0ed0072bd6e..00000000000
--- a/doc/release-notes/12112-get-default-contributor-role.md
+++ /dev/null
@@ -1 +0,0 @@
-A new API endpoint for getting the default contributor role of a collection (`GET /api/dataverses/$ID/defaultContributorRole`) was added.
\ No newline at end of file
diff --git a/doc/release-notes/12141-storage-driver-endpoints.md b/doc/release-notes/12141-storage-driver-endpoints.md
deleted file mode 100644
index 2d57da3f04d..00000000000
--- a/doc/release-notes/12141-storage-driver-endpoints.md
+++ /dev/null
@@ -1,6 +0,0 @@
-### Breaking Changes
-
-All endpoints related to storage drivers have been moved out of the Admin API.
-
-- The GET, PUT, and DELETE endpoints for `/api/admin/dataverse/{alias}/storageDriver` have been moved to `/api/dataverses/{alias}/storageDriver`. Write operations continue to be accessible only to superusers, while GET methods are public.
-- The endpoint `/api/admin/dataverse/storageDrivers` has been made public, moved, and renamed to `/api/dataverses/{alias}/allowedStorageDrivers`. Regarding the name change, this endpoint will in the future only display the storage drivers that are allowed on the specified collection. For now, it will display the entire list of available drivers on the installation.
diff --git a/doc/release-notes/12174-handle-improvements.md b/doc/release-notes/12174-handle-improvements.md
deleted file mode 100644
index 09315f352f6..00000000000
--- a/doc/release-notes/12174-handle-improvements.md
+++ /dev/null
@@ -1,5 +0,0 @@
-This release offers improved support for Handles as persistent ids.
-
-The following issues are fixed:
-- When pid registration of persistent ids for files is enabled, Dataverse will create the handle as soon as the file is created (similary to other persistent id providers) (issue #12174);
-- When a new handle is created, for a dataset or file that is still a draft, it will be reserved and registered, but not visible publicly. The handle will become visible and the redirects will start working once it is published. This is also in line with how DOI providers work (issue #8881). 
\ No newline at end of file
diff --git a/doc/release-notes/12194-ignore-exclude-email-setting-for-collections.md b/doc/release-notes/12194-ignore-exclude-email-setting-for-collections.md
deleted file mode 100644
index def993ae624..00000000000
--- a/doc/release-notes/12194-ignore-exclude-email-setting-for-collections.md
+++ /dev/null
@@ -1,2 +0,0 @@
-A new query parameter (`ignoreSettingExcludeEmailFromExport`) has been added to the ["View a Dataverse Collection"](https://guides.dataverse.org/en/latest/api/native-api.html#view-a-dataverse-collection) API (`/api/dataverses/{collectionId}`).
-This query parameter prevents the contact emails from being excluded when the setting `ExcludeEmailFromExport` is set to true and the user has EditDataverse permissions.
\ No newline at end of file
diff --git a/doc/release-notes/12224-local-contexts-rights-info-in-DataCite b/doc/release-notes/12224-local-contexts-rights-info-in-DataCite
deleted file mode 100644
index c0a4c7b4d7a..00000000000
--- a/doc/release-notes/12224-local-contexts-rights-info-in-DataCite
+++ /dev/null
@@ -1,8 +0,0 @@
-For instances enabling use of Local Contexts integration, Dataverse will now add rights information
-related to the Notices and Labels from a Local Contexts Project associated with a dataset to the metadata
-sent to DataCite (when using DataCite DOIs) and available in metadata exports (DataCite, OAI-ORE, and JSON).  
-
-It is now possible to use non-string values in the retrieval-filtering context entries for external vocabulary scripts.
-This can be used to allow filtered JSON that is not valid JSON-LD to be included in the OAI_ORE JSON-LD metadata export
- in a way that JSON-LD parsers will accept (and not ignore/drop). The OAI_ORE export version has been updated to 1.0.3 with this change.
-   
\ No newline at end of file
diff --git a/doc/release-notes/12244-fix-citations.md b/doc/release-notes/12244-fix-citations.md
deleted file mode 100644
index 12901225eb2..00000000000
--- a/doc/release-notes/12244-fix-citations.md
+++ /dev/null
@@ -1 +0,0 @@
-This release fixes a bug causing Author names of Organizations to be incorrect in styled citations (the software attempted to interpret the organization's name as a first name/last name pair).
\ No newline at end of file
diff --git a/doc/release-notes/12245-anon-guestbook-download-via-persistentid.md b/doc/release-notes/12245-anon-guestbook-download-via-persistentid.md
deleted file mode 100644
index b926a6441a1..00000000000
--- a/doc/release-notes/12245-anon-guestbook-download-via-persistentid.md
+++ /dev/null
@@ -1,4 +0,0 @@
-## Bug
-Guest requesting file download using :persistentId with guestbook response is now working.
-
-"persistentId" will be replaced by the actual fileId in the signed url that is returned by the POST call containing the guestbook response.
diff --git a/doc/release-notes/12246-guard-npe-bag-generator.md b/doc/release-notes/12246-guard-npe-bag-generator.md
deleted file mode 100644
index 12069a8fcec..00000000000
--- a/doc/release-notes/12246-guard-npe-bag-generator.md
+++ /dev/null
@@ -1 +0,0 @@
-Fixed a problem in the BagPack generator, which caused the export to fail for datasets with multiple Contact Points, of which some had no name while others did.
\ No newline at end of file
diff --git a/doc/release-notes/12258-publish-submit-contains-files.md b/doc/release-notes/12258-publish-submit-contains-files.md
deleted file mode 100644
index dd6e6d7153c..00000000000
--- a/doc/release-notes/12258-publish-submit-contains-files.md
+++ /dev/null
@@ -1,2 +0,0 @@
-## Bug: Publish and Submit for review must contain files
-When `requireFilesToPublishDataset` is set on a Dataverse a Dataset must contain files to be published or submitted for review. This fix make sure the dataset version contains files, and not just the dataset. It also adds this check to the `Submit for Review` functionality.
diff --git a/doc/release-notes/12260-get-guestbook-with-usage-and-response-counts.md b/doc/release-notes/12260-get-guestbook-with-usage-and-response-counts.md
deleted file mode 100644
index 8f2a4e58d24..00000000000
--- a/doc/release-notes/12260-get-guestbook-with-usage-and-response-counts.md
+++ /dev/null
@@ -1,2 +0,0 @@
-## API Enhancement
-API call to `/api/guestbooks/{dataverseAlias}/list` can now include `"usageCount":#` and `"responseCount":#` in the response by adding the query param "includeStats=true".
diff --git a/doc/release-notes/12267-does-not-save-guestbook-response.md b/doc/release-notes/12267-does-not-save-guestbook-response.md
deleted file mode 100644
index c30fdeeda81..00000000000
--- a/doc/release-notes/12267-does-not-save-guestbook-response.md
+++ /dev/null
@@ -1,4 +0,0 @@
-## BUG
-Fixes 2 bugs
-1. missing "gbrids" in the signed url query parameter list will no longer include "&gbrids=" without a value
-2. For SPA, when a user attempting to download files with a guestbook response has no api token but is authenticated by bearer token, a temporary api token will be generated with an expiration of 1 minute which is used for signing and decoding the signed url.
diff --git a/doc/release-notes/12268-direct-upload-support-legacy-lowercase-dois.md b/doc/release-notes/12268-direct-upload-support-legacy-lowercase-dois.md
deleted file mode 100644
index a26a4b3beaf..00000000000
--- a/doc/release-notes/12268-direct-upload-support-legacy-lowercase-dois.md
+++ /dev/null
@@ -1 +0,0 @@
-Fixed a problem with S3 direct upload to datasets which using lower- or mixed-case PID authority/identifier in the database and to datasets using an alternative identifier for file storage.
diff --git a/doc/release-notes/12313-local-reviews.md b/doc/release-notes/12313-local-reviews.md
deleted file mode 100644
index 4ca22a784ff..00000000000
--- a/doc/release-notes/12313-local-reviews.md
+++ /dev/null
@@ -1,13 +0,0 @@
-### Local Reviews
-
-Datasets can have local reviews, listable via API. A local review is a review dataset ("review" for short) that points at the URL form of a persistent ID of a dataset (e.g. itemReviewedUrl:https://doi.org/10.5072/FK2/ABCDEF) that is in the same Dataverse installation. Local reviews of a dataset can be listed via API (and we plan to build a UI for it some day).
-
-A new metadata block called "Trusted Data Dimensions and Intensities" has been added for testing. This is described in the setup instructions for review datasets.
-
-If you set `dataverse.feature.croissant-with-local-reviews` to true, local reviews will appear in the croissant and croissantSlim metadata export formats for any dataset that has local reviews. This feature is experiemental, which is why it is hidden behind a feature flag.
-
-See the guides for the new [list reviews](https://preview.guides.gdcc.io/en/develop/api/native-api.html#list-reviews) API endpoint, #12313, #12314, and #12425.
-
-## New Settings
-
-- dataverse.feature.croissant-with-local-reviews
diff --git a/doc/release-notes/12319-LocallyFAIRdata b/doc/release-notes/12319-LocallyFAIRdata
deleted file mode 100644
index afbd0e26302..00000000000
--- a/doc/release-notes/12319-LocallyFAIRdata
+++ /dev/null
@@ -1,9 +0,0 @@
-This release includes experimental support for "Locally FAIR" data.
-This feature allows publication of content that will only be visible to authorized users or groups within a Dataverse installation.
-User without authorization will not see the Locally FAIR collections, datasets, or files in search results and cannot visit their
-pages or access them via the Dataverse API.
-
-For more information, see the [Locally FAIR Data](https://guides.dataverse.org/en/latest/user/locally-fair-data.html) guide.
-
-New Config Option:
-Whether Locally FAIR content can be created is controlled by the new `dataverse.feature.allow-locally-fair-data` feature flag.
\ No newline at end of file
diff --git a/doc/release-notes/12323-get-inherited-guestbooks-list-api.md b/doc/release-notes/12323-get-inherited-guestbooks-list-api.md
deleted file mode 100644
index 89516d65653..00000000000
--- a/doc/release-notes/12323-get-inherited-guestbooks-list-api.md
+++ /dev/null
@@ -1,2 +0,0 @@
-Added 'includeInherited' to query parameters of /api/guestbooks/{ID}/list?includeInherited=true to return the Collection's Guestbooks as well as the Guestbooks of the Collections' hierarchical owners 
-Also removed the 'EditDataverse' permission requirement to get the list.
diff --git a/doc/release-notes/12325-submit-for-review-message.md b/doc/release-notes/12325-submit-for-review-message.md
deleted file mode 100644
index b233c009fb1..00000000000
--- a/doc/release-notes/12325-submit-for-review-message.md
+++ /dev/null
@@ -1,4 +0,0 @@
-## Feature
-
-Added Submit for Review dialog disclaimer messages (similar to Publish disclaimer messages). Can be set using setting :SubmitForReviewDatasetDisclaimerText
- Also added :DatasetSubmitForReviewPopupCustomText to allow for custom text to be displayed in the dialog similar to the Publish dialog
diff --git a/doc/release-notes/12340-timing-issue-guestbook-response.md b/doc/release-notes/12340-timing-issue-guestbook-response.md
deleted file mode 100644
index 39d40e5d3db..00000000000
--- a/doc/release-notes/12340-timing-issue-guestbook-response.md
+++ /dev/null
@@ -1,2 +0,0 @@
-## BUG 
-Timing issue fixed where user only had a few seconds instead of a minute to call the File download API after POSTing the guestbook response
diff --git a/doc/release-notes/12358-enable-s3-multipart-upload.md b/doc/release-notes/12358-enable-s3-multipart-upload.md
deleted file mode 100644
index 22365fbbaec..00000000000
--- a/doc/release-notes/12358-enable-s3-multipart-upload.md
+++ /dev/null
@@ -1 +0,0 @@
-Fixed a defect that caused upload of files larger than 1G to fail silently for S3 storage, unless direct upload was used. 
\ No newline at end of file
diff --git a/doc/release-notes/12386-manage-guestbook-apis.md b/doc/release-notes/12386-manage-guestbook-apis.md
deleted file mode 100644
index ed28680720a..00000000000
--- a/doc/release-notes/12386-manage-guestbook-apis.md
+++ /dev/null
@@ -1,12 +0,0 @@
-## Feature - Manage Guestbook
-
-This feature adds 2 new APIs to help manage Guestbooks and Guestbook Responses.
-
-
-This API allows the user to make edits to an existing Guestbook, including adding and removing Custom Guestbook Questions.
-
-`curl -PUT -H  "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/guestbooks/{ID}" -d "$JSON"`
-
-This API allows the user to retrieve Guestbook Responses for a specific Guestbook within a Collection. Optional pagination parameters can be added to limit the number of results, as this can get very large.
-
-`curl -H  "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/guestbooks/$ID/responses?limit10&offset=0"`
diff --git a/doc/release-notes/12415-remove-testingest-class.md b/doc/release-notes/12415-remove-testingest-class.md
deleted file mode 100644
index 8eae307f386..00000000000
--- a/doc/release-notes/12415-remove-testingest-class.md
+++ /dev/null
@@ -1 +0,0 @@
-Class TestIngest was removed as it was no longer being used
diff --git a/doc/release-notes/12417-remove-meta-class.md b/doc/release-notes/12417-remove-meta-class.md
deleted file mode 100644
index 83f3f683a83..00000000000
--- a/doc/release-notes/12417-remove-meta-class.md
+++ /dev/null
@@ -1 +0,0 @@
-Class Meta was removed as it was no longer being used
diff --git a/doc/release-notes/12446-fix-guestbook-response-parsing.md b/doc/release-notes/12446-fix-guestbook-response-parsing.md
deleted file mode 100644
index f9102cdb260..00000000000
--- a/doc/release-notes/12446-fix-guestbook-response-parsing.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## Bug ##
-
-Guestbook response parsing now allows a textarea value to be a string along with an array.
diff --git a/doc/release-notes/360-modify-notvalid-deaccession-reason.md b/doc/release-notes/360-modify-notvalid-deaccession-reason.md
deleted file mode 100644
index fcfba4dfcd0..00000000000
--- a/doc/release-notes/360-modify-notvalid-deaccession-reason.md
+++ /dev/null
@@ -1,16 +0,0 @@
-# Language change for file.deaccessionDialog.reason.selectItem.notValid
-
-"Not a valid dataset." is being changed to "Not valid. This dataset does not comply with repository policies."
-This is the default English language version. For installations using customized languages, replacing the Bundle.properties file, please follow these manual instructions to make this modification, if desired.
-
-Make the change to the Bundle_##.properties file with the new verbiage. Either locally or as an update to [dataverse-language-packs Repo](https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs/tree/develop)
-
-The SQL statements to modify the datasets is:
-
-- `UPDATE dvobject SET indextime=null WHERE id in (SELECT dataset_id FROM datasetversion WHERE deaccessionnote='Not a valid dataset.');`
-
-- `UPDATE datasetversion SET deaccessionnote='Not valid. This dataset does not comply with repository policies.' WHERE deaccessionnote='Not a valid dataset.';`
-
-Once the database is updated the Solr indexes need to be rebuilt using the following Admin API:
-
-- `curl http://localhost:8080/api/admin/index`
diff --git a/doc/release-notes/6.11-release-notes.md b/doc/release-notes/6.11-release-notes.md
new file mode 100644
index 00000000000..167fc13396e
--- /dev/null
+++ b/doc/release-notes/6.11-release-notes.md
@@ -0,0 +1,289 @@
+# Dataverse 6.11
+
+Please note: To read these instructions in full, please go to https://github.com/IQSS/dataverse/releases/tag/v6.11 rather than the [list of releases](https://github.com/IQSS/dataverse/releases), which will cut them off.
+
+This release brings new features, enhancements, and bug fixes to Dataverse. Thank you to all of the community members who contributed code, suggestions, bug reports, and other assistance across the project!
+
+## Release Highlights
+
+Highlights for Dataverse 6.11 include:
+
+- Locally FAIR data
+- New expanded geospatial metadata block
+- Submit for Review improvements
+- Show historical file access requests
+- Local reviews
+- New and improved APIs
+- Bug fixes
+
+### Locally FAIR Data
+
+This release includes experimental support for "Locally FAIR" data. When enabled, this feature allows publication of content that will be visible only to authorized users or groups within a Dataverse installation. Users without authorization will not see the Locally FAIR collections, datasets, or files in search results and cannot visit their pages or access them via the Dataverse API.
+
+For more information, see [Locally FAIR Data](https://guides.dataverse.org/en/6.11/user/dataverse-management.html#locally-fair) in the guides and #12319.
+
+### New Expanded Geospatial Metadata Block
+
+This release introduces a major enhancement to geospatial data support with the addition of an expanded Geospatial Metadata Block, designed to improve how researchers describe, share, and discover geospatial datasets.
+
+This new expanded metadata block aligns with the international ISO 19115 standard for describing geographic data.
+
+- Includes 22 new metadata fields to provide more detailed and standardized descriptions of geospatial data (e.g. vector, raster, mixed or multi-format geospatial collections)
+- Incorporates and extends current metadata elements (Geographic Coverage and Geographic Bounding Box)
+- Ensures backward compatibility while significantly improving metadata description capabilities
+
+See [the guides](https://guides.dataverse.org/en/6.11/user/appendix.html#supported-metadata), #10398, and #11507.
+
+### Submit for Review Improvements
+
+- A disclaimer message and custom text can be added to the "Submit for Review" dialog, similar to Publish disclaimer messages. See [:SubmitForReviewDatasetDisclaimerText](https://guides.dataverse.org/en/6.11/installation/config.html#submitforreviewdatasetdisclaimertext), [:DatasetSubmitForReviewPopupCustomText](https://guides.dataverse.org/en/6.11/installation/config.html#datasetsubmitforreviewpopupcustomtext), #12325 and #12373.
+- When `requireFilesToPublishDataset` (added in #10994 in Dataverse 6.6) is set on a collection, a dataset must contain files for the Submit for Review button to appear. As before, publishing is also prevented if no files are present. See #12258 and #12266.
+
+### Show Historical File Access Requests
+
+A new checkbox called "Show Historical Requests" has been added to the permissions page for a data file. Checking the box will show the number of times each user has been granted or denied access. See #8013 and #12012.
+
+### Local Reviews
+
+Datasets can have local reviews, listable via API. A local review is a review dataset ("review" for short) that points at the URL form of a persistent ID of a dataset (e.g. itemReviewedUrl:https://doi.org/10.5072/FK2/ABCDEF) that is in the same Dataverse installation. Local reviews of a dataset can be listed via API (and we plan to build a UI for it some day).
+
+A new metadata block called "Trusted Data Dimensions and Intensities" has been added for testing. This is described in the setup instructions for review datasets.
+
+If you set `dataverse.feature.croissant-with-local-reviews` to true, local reviews will appear in the `croissant` and `croissantSlim` metadata export formats for any dataset that has local reviews. This feature is experimental, which is why it is hidden behind a feature flag.
+
+See the guides for the new [list reviews](https://guides.dataverse.org/en/6.11/api/native-api.html#list-reviews) API endpoint, #12313, #12314, and #12425.
+
+## Features Added
+
+These are features that weren't already mentioned under "highlights" above.
+
+### Original Tabular File Format Shown (Rather Than .tab)
+
+In previous releases of Dataverse, the file, dataset, and collection pages showed the .tab version of tabular files (a plain text preservation-friendly copy). This has been changed to show the original format instead (e.g. Excel, Stata, etc.). The .tab version is still available from the download menu. See #7956 and #12145.
+
+### Croissant 1.1 (Summary Statistics)
+
+The Croissant metadata export format has been updated from version 1.0 to 1.1.
+
+Summary statistics (mean, min, max, etc.) are now included for tabular files that were successfully ingested.
+
+You can download an example Croissant file from the [Supported Metadata Export Formats](https://guides.dataverse.org/en/6.11/user/dataset-management.html#supported-metadata-export-formats) section of the guides.
+
+Minor backward-incompatible changes were made, which are noted below. See #12014 and #12214.
+
+### Local Contexts Improvements
+
+For instances that have enabled the Local Contexts integration, Dataverse will now add rights information related to the Notices and Labels from a Local Contexts Project associated with a dataset to the metadata sent to DataCite (when using DataCite DOIs) and available in metadata exports (DataCite, OAI-ORE, and JSON).
+
+In addition, it is now possible to use non-string values in the retrieval-filtering context entries for external vocabulary scripts. This can be used to allow filtered JSON that is not valid JSON-LD to be included in the OAI_ORE JSON-LD metadata export in a way that JSON-LD parsers will accept (and not ignore/drop). The OAI_ORE export version has been updated to 1.0.3 with this change. See the [guides](https://guides.dataverse.org/en/6.11/installation/localcontexts.html#configuration) and #12224.
+
+### Improved Support for Handles as Persistent IDs
+
+The following issues were addressed in #12366:
+
+- When PID registration of persistent IDs for files is enabled, Dataverse will create the handle as soon as the file is created (similar to other persistent ID providers) (issue #12174);
+- When a new handle is created for a dataset or file that is still a draft, it will be reserved and registered, but not visible publicly. The handle will become visible and the redirects will start working once it is published. This is also in line with how DOI providers work (issue #8881). 
+
+## Bug Fixes
+
+- We fixed a defect that caused upload of files larger than 1 GB to fail silently for S3 storage, unless direct upload was used. See #12358.
+- When using the Access API to download files from a dataset that has a guestbook, and when using the dataset's :persistentId instead of its database id, the returned signedUrl immediately failed with a 401 error. This bug was fixed so that the signedUrl correctly returns the files. Using the dataset's and datafile's database ids, instead of its :persistentId, was unaffected by this bug and continues to work. See #12245 and #12363.
+- When the "modifyRegistrationMetadata" API was used, some datasets with UTF-8 characters were being unnecessarily updated in DataCite. This has been resolved by switching from the DataCite MDS API to its JSON API. See the upgrade instructions below, #12070, and #12270.
+- Fixed a problem with S3 direct upload to datasets that use lower- or mixed-case PID authority/identifier in the database and to datasets using an alternative identifier for file storage. See #12268. 
+- The bug "Search API doesn't return image_url after newly created dataset is published" was fixed in the following manner. The dataset thumbnail will be created automatically when a dataset is published under the following conditions: the dataset has no existing thumbnail; the dataset has image files that can be converted to a thumbnail the Feature Flag "disable-dataset-thumbnail-autoselect" is not enabled. See #11588 and #12403.
+- A bug in the BagPack generator, which caused the export to fail for datasets with multiple Contact Points, of which some had no name while others did, has been fixed. See #12246.
+- Two guestbook API bugs were fixed. First, missing "gbrids" in the signed URL query parameter list will no longer include "&gbrids=" without a value. Second, when a user attempting to download files with a guestbook response has no API token but is authenticated by bearer token, a temporary api token will be generated with an expiration of 1 minute which is used for signing and decoding the signed URL. See #12267, #12277, and #12279
+- We fixed a timing issue fixed where user only had a few seconds instead of a minute to call the file download API after POSTing the guestbook response. See #12340 and #12341.
+
+## Other Changes
+
+- A [list of Dataverse features](https://guides.dataverse.org/en/6.11/admin/features.html) has been added to the guides, thanks to the [Documentation Working Group](https://www.gdcc.io/working-groups/documentation.html) over many meetings (recorded, if you're interested!). Historically, the list of features has been maintained at [dataverse.org/software-features](https://dataverse.org/software-features) but by moving [the list](https://guides.dataverse.org/en/6.11/admin/features.html) into the guides, we hope to keep it up-to-date with help from the community. To make improvements, please feel free to open issues, make pull requests, [discuss](https://dataverse.zulipchat.com/#narrow/channel/446770-docs/topic/list.20of.20features/with/604499830) in Zulip, and join a Documentation Working Group meeting! See #11998 and #12000.
+- The [Big Data Support](https://guides.dataverse.org/en/6.11/installation/big-data-support.html) page has been moved from the Developer Guide to the Installation Guide. See #12151.
+- The deaccession reason "Not a valid dataset." has been changed to "Not valid. This dataset does not comply with repository policies." See the Bundle.properties key file.deaccessionDialog.reason.selectItem.notValid and #11985.
+
+## API Updates
+
+- New APIs have been added called [Update the Metadata and Instructions of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-metadata-and-instructions-of-a-template), [Update the License or Terms Of Use of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-license-or-terms-of-use-of-a-template), and [Update the Terms Of Access of a Template](https://guides.dataverse.org/en/6.11/api/native-api.html#update-the-terms-of-access-of-a-template). See #11912 and #12159.
+- A new API endpoint for getting the default contributor role of a collection was added. See [the guides](https://guides.dataverse.org/en/6.11/api/native-api.html#get-default-role-assigned-to-user-creating-a-dataset-in-a-dataverse-collection) and #12112. 
+- A new API has been added to get citations in various formats such as EndNote, RIS, BibTeX, and CSL. Previously this functionality was only available via the UI. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#citation-get-citation-in-other-formats), #11733 and #12238.
+- An API endpoint was added that allows the user to make edits to an existing Guestbook, including adding and removing custom guestbook questions: `curl -X PUT -H  "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/guestbooks/{ID}" -d "$JSON"`. Another API was added that allows the user to retrieve guestbook responses for a specific guestbook within a collection. Optional pagination parameters can be added to limit the number of results, as this can get very large: `curl -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/guestbooks/$ID/responses?limit10&offset=0"`. See #12386 and #12395.
+- The API endpoint `/api/guestbooks/{dataverseAlias}/list` can now include `"usageCount":#` and `"responseCount":#` in the response by adding the query param "includeStats=true". See [the guides](https://guides.dataverse.org/en/6.11/api/native-api.html#get-a-list-of-guestbooks-for-a-dataverse-collection), #12260, and #12269.
+- A new query parameter (`ignoreSettingExcludeEmailFromExport`) has been added to the ["View a Dataverse Collection"](https://guides.dataverse.org/en/6.11/api/native-api.html#view-a-dataverse-collection) API (`/api/dataverses/{collectionId}`). This query parameter prevents the contact emails from being excluded when the setting `:ExcludeEmailFromExport` is set to true and the user has EditDataverse permissions. See #12194 and #12195.
+- All API endpoints that return information about role assignments (such as `/api/dataverses/$ID/assignments`) now include additional fields in their JSON responses: `assigneeName`, `roleDescription`, `definitionPointName`, `definitionPointType`, and `definitionPointGlobalId` (if available). See #11920.
+- The `/datafile/{id}/listRequests` API has been extended to show request history. See [the guides](https://guides.dataverse.org/en/6.11/api/dataaccess.html#list-file-access-requests), #8013 and #12012.
+- "includeInherited" was added as a query parameter of `/api/guestbooks/{ID}/list?includeInherited=true` to return the collection's guestbooks as well as the guestbooks of the collections' hierarchical owners. Also the "EditDataverse" permission requirement to get the list was removed. See #12323 and #12326.
+- Guestbook response parsing now allows a textarea value to be a string along with an array. See #12446 and #12447.
+- The classes TestIngest (#12415) and Meta (#12417) were removed as they were no longer being used.
+
+## Security Updates
+
+This release contains important security updates. If you are not receiving security advisories, please sign up by following [the steps](https://guides.dataverse.org/en/latest/installation/config.html#ongoing-security-of-your-installation) in the guides.
+
+As we [announced](https://groups.google.com/g/dataverse-community/c/wqSQYH_fSlA/m/6xcGh0CnAgAJ) on the mailing list, we are experimenting with sending security advisories via Mailchimp. The sign up steps are the same.
+
+We would like to thank Pablo Picurelli Ortiz and Josh Dow for notifying us about vulnerabilities that were fixed in this release.
+
+## Backward Incompatible Changes
+
+Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/latest/api/changelog.html) for a list of backward-incompatible API changes.
+
+- The `GET /api/access/datafile/{id}/userPermissions` endpoint now requires authentication.
+- The `GET /api/mydata/retrieve` endpoint, if the search returns no data, now includes the "data" block with 0 results. The message that was returned in "error_message" will be returned in "message" and the "success" will be `true`. All other errors will continue to reply with "success":false and the error message in "error_message". See #11447 and #12256.
+- The Croissant metadata export format has been updated from version 1.0 to 1.1, which is reflected in the "conformsTo" property. The unused "wd" property has been dropped.
+- All endpoints related to storage drivers have been moved out of the Admin API. See #12141 and #12182.
+  - The GET, PUT, and DELETE endpoints for `/api/admin/dataverse/{alias}/storageDriver` have been moved to `/api/dataverses/{alias}/storageDriver`. Write operations continue to be accessible only to superusers, while GET methods are public.
+  - The endpoint `/api/admin/dataverse/storageDrivers` has been made public, moved, and renamed to `/api/dataverses/{alias}/allowedStorageDrivers`. Regarding the name change, this endpoint will in the future only display the storage drivers that are allowed on the specified collection. For now, it will display the entire list of available drivers on the installation.
+
+## End-Of-Life (EOL) Announcements
+
+### PostgreSQL 13 Reached EOL on 13 November 2025
+
+We mentioned this in the Dataverse [6.6](https://github.com/IQSS/dataverse/releases/tag/v6.6), [6.8](https://github.com/IQSS/dataverse/releases/tag/v6.8), [6.9](https://github.com/IQSS/dataverse/releases/tag/v6.9), and [6.10](https://github.com/IQSS/dataverse/releases/tag/v6.10) release notes, but as a reminder, according to https://www.postgresql.org/support/versioning/ PostgreSQL 13 reached EOL on 13 November 2025. As stated in the [Installation Guide](https://guides.dataverse.org/en/6.11/installation/prerequisites.html#postgresql), we recommend running PostgreSQL 16 since it is the version we test with in our continuous integration ([since](https://github.com/gdcc/dataverse-ansible/commit/8ebbd84ad2cf3903b8f995f0d34578250f4223ff) February 2025). The [Dataverse 5.4 release notes](https://github.com/IQSS/dataverse/releases/tag/v5.4) explained the upgrade process from 9 to 13 (e.g. pg_dumpall, etc.) and the steps will be similar. If you have any problems, please feel free to reach out (see "getting help" in these release notes).
+
+## Notes for Dataverse Installation Administrators
+
+### CORS Filter Fix and Docs
+
+We fixed an inconsistency where the `CorsFilter` was not always being invoked when accessing `/api/...` endpoints, preventing these endpoints from being used from webapps even when CORS was properly configured. In addition, the [documentation](https://guides.dataverse.org/en/6.11/installation/config.html#cross-origin-resource-sharing-cors) related to how certain Dataverse features depend on proper CORS configuration has been extended and improved. See #12151 and #12161.
+
+## New Settings
+
+### New JVM Options (MicroProfile Config Settings)
+
+- dataverse.feature.allow-locally-fair-data
+- dataverse.feature.croissant-with-local-reviews
+
+### New Database Settings
+
+- :DatasetSubmitForReviewPopupCustomText
+- :SubmitForReviewDatasetDisclaimerText
+
+## Updates for Documentation Writers
+
+The dependencies "sphinx-reredirects" and "sphinx-design" have been added. Please re-run the `pip install -r requirements.txt` setup [step](https://guides.dataverse.org/en/6.11/contributor/documentation.html#building-the-guides-with-sphinx) to update your environment. Otherwise you will see a "could not import extension" error.
+
+## Updates for Developers
+
+Developers making pull requests against the main "dataverse" project on GitHub can now see for themselves which API tests are failing, if any. Look for a GitHub Action called "Container Integration Tests Workflow". See #9916 and #12368.
+
+New "fast redeploy" scripts have been added for the backend. See [the guides](https://guides.dataverse.org/en/6.11/container/dev-usage.html#fast-redeploy-command-line), #10156, and [Zulip](https://dataverse.zulipchat.com/#narrow/channel/379673-dev/topic/fast.20redeploy.20with.20docker.20compose/near/553715282). Please note that this solution is being further improved in #12467.
+
+## Complete List of Changes
+
+For the complete list of code changes in this release, see the [6.11 milestone](https://github.com/IQSS/dataverse/issues?q=milestone%3A6.11+is%3Aclosed) in GitHub.
+
+## Getting Help
+
+For help with upgrading, installing, or general questions please see [getting help](https://guides.dataverse.org/en/latest/installation/intro.html#getting-help) in the Installation Guide.
+
+## Installation
+
+If this is a new installation, please follow our [Installation Guide](https://guides.dataverse.org/en/latest/installation/). Please don't be shy about [asking for help](https://guides.dataverse.org/en/latest/installation/intro.html#getting-help) if you need it!
+
+Once you are in production, we would be delighted to update our [map of Dataverse installations around the world](https://dataverse.org/installations) to include yours! Please [create an issue](https://github.com/IQSS/dataverse-installations/issues) or email us at support@dataverse.org to join the club!
+
+You are also very welcome to join the [Global Dataverse Community Consortium](https://www.gdcc.io) (GDCC).
+
+## Upgrade Instructions
+
+Upgrading requires a maintenance window and downtime. Please plan accordingly, create backups of your database, etc.
+
+Note: These instructions assume that you are upgrading from the immediate previous version. That is to say, you've already upgraded through all the 6.x releases and are now running Dataverse 6.10.1. See [tags on GitHub](https://github.com/IQSS/dataverse/tags) for a list of versions. If you are running an earlier version, the only supported way to upgrade is to progress through the upgrades to all the releases in between before attempting the upgrade to this version.
+
+If you are running Payara as a non-root user (and you should be!), **remember not to execute the commands below as root**. By default, Payara runs as the `dataverse` user. In the commands below, we use sudo to run the commands as a non-root user.
+
+Also, we assume that Payara is installed in `/usr/local/payara7`. If not, adjust as needed.
+
+1. List deployed applications.
+
+   `/usr/local/payara7/bin/asadmin list-applications`
+
+1. Undeploy the previous version (should match "list-applications" above).
+
+   `/usr/local/payara7/bin/asadmin undeploy dataverse-6.10.1`
+
+1. Deploy the Dataverse 6.11 war file.
+
+   `wget https://github.com/IQSS/dataverse/releases/download/v6.11/dataverse-6.11.war`
+
+   `sudo -u dataverse /usr/local/payara7/bin/asadmin deploy dataverse-6.11.war`
+
+1. Check that you get a version number from Dataverse.
+
+   This is just a sanity check that Dataverse has been deployed properly.
+
+   `curl http://localhost:8080/api/info/version`
+
+1. Update the geospatial metadata block.
+
+   `wget https://raw.githubusercontent.com/IQSS/dataverse/refs/tags/v6.11/scripts/api/data/metadatablocks/geospatial.tsv`
+
+   `curl http://localhost:8080/api/admin/datasetfield/load -H "Content-type: text/tab-separated-values" -X POST --upload-file geospatial.tsv`
+
+1. Update Solr schema.
+
+   Due to changes in the Solr schema (the addition of geospatial fields), updating the Solr schema and reindexing is required.
+
+   First, back up you existing `schema.xml` file.
+
+   `cp /usr/local/solr/solr-9.8.0/server/solr/collection1/conf/schema.xml /usr/local/solr/solr-9.8.0/server/solr/collection1/conf/schema.xml.orig`
+
+   (Note that Docker-based installations use this directory: `solr/data/data/collection1/conf/schema.xml`.)
+
+   If you do not have any custom metadata blocks, you can simply download an updated `schema.xml` file and put it into place.
+
+   `wget https://raw.githubusercontent.com/IQSS/dataverse/v6.11/conf/solr/schema.xml`
+
+   `cp schema.xml /usr/local/solr/solr-9.8.0/server/solr/collection1/conf`
+
+   Reload the Solr core.
+
+   `curl "http://localhost:8983/solr/admin/cores?action=RELOAD&core=collection1"`
+
+   If you do have custom metadata blocks, run the `update-fields.sh` script that we supply. The example below shows the default path for a non-Docker installation, but adjust the path as necessary.
+
+   `wget https://raw.githubusercontent.com/IQSS/dataverse/v6.11/conf/solr/update-fields.sh`
+
+   `chmod +x update-fields.sh`
+
+   `curl "http://localhost:8080/api/admin/index/solr/schema" | ./update-fields.sh /usr/local/solr/solr-9.8.0/server/solr/collection1/conf/schema.xml`
+
+   Reload the Solr core
+
+   `curl "http://localhost:8983/solr/admin/cores?action=RELOAD&core=collection1"`
+
+1. Reindex Solr.
+
+   Solr needs to be reindexed because of the change to deaccessionDialog.reason.selectItem.notValid in Bundle.properties (#11985).
+
+   `curl http://localhost:8080/api/admin/index`
+
+1. Re-export metadata export formats.
+
+   We re-export because the Croissant format was updated.
+
+   `curl http://localhost:8080/api/admin/metadata/reExportAll`
+
+1. For installations with internationalization or text customizations:
+
+   Please remember to update translations via [Dataverse language packs](https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs).
+
+   If you have text customizations you can get the latest English files from <https://github.com/IQSS/dataverse/tree/v6.11/src/main/java/propertyFiles>.
+
+   Note that deaccessionDialog.reason.selectItem.notValid was updated. See #11985.
+
+1. For installations using DataCite, ensure the DataCite REST API URL (now required) is configured:
+
+   Incremental improvements have been made to the process of registering dataset metadata with DataCite. If your instance is using DataCite, please make sure you have a valid DataCite REST API URL configured, since it is now required.
+
+   The JVM options in question are `dataverse.pid.*.datacite.rest-api-url` if the recommended, new-style PID configuration is used, or `doi.dataciterestapiurlstring` if the legacy settings are in place. In the latter case however, this is a good occasion to switch to the new configuration setup.
+
+   For installations using registered DataCite authorities in production the URL should be:
+
+   `<jvm-options>-Ddataverse.pid.<providername>.datacite.rest-api-url=https://api.datacite.org</jvm-options>`
+
+   Or, for test and development instances:
+
+   `<jvm-options>-Ddataverse.pid.<providername>.datacite.rest-api-url=https://api.test.datacite.org</jvm-options>`
+
+   See [the guides](https://guides.dataverse.org/en/6.11/installation/config.html#datacite-specific-settings), #12070 and #12270.
diff --git a/doc/release-notes/7956-show_original_file_format.md b/doc/release-notes/7956-show_original_file_format.md
deleted file mode 100644
index eea80f58fc4..00000000000
--- a/doc/release-notes/7956-show_original_file_format.md
+++ /dev/null
@@ -1,2 +0,0 @@
-This release changes the display behavior of the file, dataset and collection ("dataverse") pages for tabular files. They will show the original file name and information, and will allow editing of the original file name. The ingested *.tab version is still available from the download menu. 
- 
diff --git a/doc/release-notes/8013-history-of-access-request-available-via-api.md b/doc/release-notes/8013-history-of-access-request-available-via-api.md
deleted file mode 100644
index 14ebe52f9f7..00000000000
--- a/doc/release-notes/8013-history-of-access-request-available-via-api.md
+++ /dev/null
@@ -1,8 +0,0 @@
-### Feature: Extend List File Access Requests API ###
-
-Added ability to get access request history via the `/datafile/{id}/listRequests` API. The API returns a list of users/groups where the request for access is waiting for an accept or reject. Already accepted or rejected requests are not returned.
-
-By adding the flag 'includeHistory=true' all of the requests will be returned. Pagination is also implemented in this feature. Adding a start page parameter and max list size (`&start=0` and `&per_page=20`) can limit the amount of data being returned.
-
-See https://guides.dataverse.org/en/latest/api/dataaccess.html#list-file-access-requests
-
diff --git a/doc/release-notes/cors-filter-fix.md b/doc/release-notes/cors-filter-fix.md
deleted file mode 100644
index 6acb665fe26..00000000000
--- a/doc/release-notes/cors-filter-fix.md
+++ /dev/null
@@ -1,9 +0,0 @@
-## CORS Filter Fix
-
-Fixed an inconsistency where the `CorsFilter` was not always being invoked when accessing `/api/...` endpoints, preventing these endpoints from being used from webapps even when CORS was properly configured. See #12151.
-
-In addition, the documentation around the Dataverse features regarding CORS has been extended and improved. The "Big Data" page has been moved from the development section to the installation section of the guides. See #12161.
-
-## Updates for Documentation Writers
-
-A new dependency called "sphinx-reredirects" has been added. Please re-run the `pip install -r requirements.txt` setup [step](https://dataverse-guide--12151.org.readthedocs.build/en/12151/contributor/documentation.html#building-the-guides-with-sphinx) to update your environment. Otherwise you might see an error like `Could not import extension sphinx_reredirects`.