Release 6.6 #11355
Merged
Release 6.6 #11355
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tativeDataRepository/dataverse.git into IQSS/11126-Payara6.2024.12
…xtVocabFix IQSS/11242 ExternalIdentifier fix
…ate-field-option Revert "10476 display on create field option"
API Changelog: move version note to 6.6 where it belongs
…ayara6.2024.12 Return to Author failure
API Guide: don't interleave "Dataset Version Notes" with "Dataset Types"
…S-CSL Clean up JSON CSL elements
…ion-new Metadata fields can be "display on create" per collection
Co-authored-by: Omer Fahim <[email protected]>
…76-display-on-create-field-option-new DisplayOnCreate Fixes
6.6 release notes
Co-authored-by: Philip Durbin <[email protected]>
Release 6.6
|
📦 Pushed preview images as 🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Which issue(s) this PR closes:
Special notes for your reviewer:
Suggestions on how to test this:
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation: