2.32.0 Release

[robyngit]

This issue is to track the process of the next MetacatUI release:

• Draft release notes
• Reserve a new DOI
• Replace @since 0.0.0 with @since 2.32.0 in all of /src/ folder
• Change the version number to the new version in:
  • index.html
  • package.json
  • docs/_config.yml
  • docs/index.md (citation)
  • readme (citation)
  • helm/Chart.yaml (appVersion)
• Update the helm chart version in helm/Chart.yaml (this uses a different versioning scheme) (the version field not the appVersion field)
• Change to DOI in:
  • docs/index.md
  • readme
• Rebuild docs (npm run docs)
  • Check the new doc site
• Add and commit "Change version to 2.32.0 and new doc build"
• Make a PR to merge develop into main
• Once approved, merge the PR locally so as to avoid a merge commit in main that is not in develop:

  git checkout main
  git merge develop
  git push

• Tag the new release:

  git tag -a 2.32.0 -m "MetacatUI 2.32.0"
  git push origin 2.32.0

• go to GitHub.com, make it a release:
  • Go to releases & cick draft a new release. Choose 2.32.0 tag we just made.
  • Put in the release notes
  • add images, etc
  • publish
• Deploy MetacatUI to the various nodes
• Make announcements
• Update the DOI record to resolve to the SH permalink
  • archive new release with Software Heritage (SH) - (Click the "Save again" button to request a new snapshot)
  • once archived, get the new SH ID and the permalink (Click on the red "Permalinks" button on the far right of the SH page)
  • Copy the old DataCite XML (from https://ezid.cdlib.org/manage/display_xml/doi:___) and manually update it with the following:
    • the new DOI
    • the old DOI in the <relatedIdentifier relatedIdentifierType="DOI" relationType="IsNewVersionOf"> element
    • the new Software Heraitage ID in the <alternateIdentifier alternateIdentifierType="https://registry.identifiers.org/registry/swh"> element
    • the new version number in the <version> element and in the <title> element
    • the date that the DOI was reserved in the <date dateType="Created"> element
    • any newly identified contributors (ensure we include their ORCIDs)
    • any new funding sources
  • Upload the new DataCite XML
    • ezid3.py can be used for this step, described here: Add a citation for this repo metacat#1480 (comment)
  • update the DOI record to resolve to the SH permalink

[robyngit]

New DOI:
doi:10.18739/A23F4KQ2H
https://doi.org/10.18739/A23F4KQ2H