extra heads up about payara/dv compat

Author: pdurbin

doc/release-notes/6.9-release-notes.md

@@ -118,6 +118,7 @@ This release contains important security updates such as an upgrade to Payara (#
 
 Generally speaking, see the [API Changelog](https://guides.dataverse.org/en/latest/api/changelog.html) for a list of backward-incompatible API changes.
 
+- This release of Dataverse requires an upgrade to Payara. Please be aware that you need to upgrade Payara and Dataverse at the same time because older versions of Dataverse are not compatible with newer versions of Payara. See upgrade instructions for details.
 - CORS is no longer enabled by default. See the upgrade instructions for details as well as #11745.
 - 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.
 - 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.