Finalize v2.0.0 release notes - #22
Merged
Merged
Conversation
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
1 participant
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.
Cosa cambia
Aggiorna la nota
release/v2.0.0.mddopo l'approvazione esplicita delmaintainer, eliminando l'indicazione ormai obsoleta che tag e release non
fossero ancora autorizzati.
Impatto
La release resta una prerelease perché il repository dichiara
operational_data_readiness: experimental_non_official.Nessun dataset o asset generato viene modificato.
Verifica
git diff --checkrelease/v2.0.0.mdDopo il merge, il tag annotato
v2.0.0verrà creato sul commit integrato e ilworkflow Release costruirà, validerà, attesterà e pubblicherà i nove asset.