merge from 6.6-release-branch to master#11649
Merged
Conversation
…tativeDataRepository/dataverse.git into IQSS/11126-Payara6.2024.12
…xtVocabFix IQSS/11242 ExternalIdentifier fix
…ate-field-option Revert "10476 display on create field option"
…ion-new Metadata fields can be "display on create" per collection
…76-display-on-create-field-option-new DisplayOnCreate Fixes
6.6 release notes
Co-authored-by: Philip Durbin <philip_durbin@harvard.edu>
Release 6.6
landreev
approved these changes
Jul 17, 2025
github-project-automation
Bot
moved this from Ready for Review ⏩
to Merged 🚀
in IQSS Dataverse Project
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
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:
We have force-pushed master back to v6.5 and are now (in this pull request), re-doing the v6.6 release. The complete plan can be found here: https://docs.google.com/document/d/1oit6LLDUWpNpV_uWveOMvdwDsaUey-74ehvzCZp1f3k/edit?usp=sharing
Which issue(s) this PR closes:
None.
Special notes for your reviewer:
Normally we merge develop to master but develop is way ahead of v6.6. In fact it's ready for the v6.7 release. So we're using this "6.6-release-branch" instead of "develop". The "6.6-release-branch" is branched from the latest commit we want in v6.6, which is this one: b106bd0
Suggestions on how to test this:
https://guides.dataverse.org/en/6.6/developers/making-releases.html says to wait for important tests to pass but Jenkins/Ansible has already been bumped to v6.7 so I'm sure it will fail.
Maybe we don't do any testing. Not sure. 🤷