[REL] - 2024.11.2

[soapy1]

Release details

Scheduled release date - <2024/11/26>

Release captain responsible - @soapy1

1. Pre-flight checks

• Ensure there are no open issues with a block-release ⛔️ label

2. Prepare the codebase for a new release

• Create a new git branch for the release git checkout -b release-2024.9.1

  • Prepare the branch just in case git clean -fxdq

• Bump conda-store version in conda-store/conda-store/__init__.py

• Bump conda-store-server version in conda-store-server/conda-store-server/__init__.py

• Update the conda-store-ui version used in conda-store-server conda-store-server/hatch_build.py

• Update the CHANGELOG.md file with the new version, release date, and relevant changes¹.

• Check the version locally with hatch version

• Build and test locally

  • For conda-store and conda-store-server:

    # Note you will need to run this twice, once for each package
    cd conda-store # or cd conda-store-server
    hatch build
    twine check dist/*
    hatch clean

  • After building conda-store-server and before hatch clean run the server in standalone mode:

    cd conda-store-server
    conda-store-server --standalone

    To do a manual inspection of the build and ui vendoring process.

• Make a release commit: git commit -m 'REL - 2024.9.1'

• Push the release (REL) commit git push upstream main

• If a release candidate is needed, tick this box when we're ready for a full release.

3. Make the release

• Start a new GitHub release
  • Call the release the current version, e.g. 2024.9.1
  • In the Choose a Tag: dropdown, type in the release name (e.g., 2024.9.1) and click "Create new tag"
  • In the Target: dropdown, pin it to the release commit you've recently pushed.
  • Add release notes in the field below¹; you can copy/paste the Changelog from the CHANGELOG.md file.
• Confirm that the release completed
  • The release GitHub action job has completed successfully in the actions tab.
  • The conda-store PyPI version is updated
  • The conda-store-server PyPI version is updated
  • The Docker images have been published
• Update the conda-forge feedstock version through a PR or review and merge the regro-bot PR.
  • If needed - update meta.yaml or recipe.yaml and re-render the feedstock.
• Open a follow-up PR to bump conda-store and conda-store-server versions to the next dev-release number (for example 2024.10.1).
• Open a follow-up PR to bump the conda-store-server version in the conda-store-ui compose file.
• Celebrate, you're done! 🎉

Footnotes

1. If you wish, use github-activity to generate a Changelog, e.g. github-activity conda-incubator/conda-store --since 2024.9.1 --until 2023.10.1. ↩ ↩²

[trallard]

Noting that this release is blocked until there is a resolution to conda-incubator/conda-store-ui#443 and a corresponding conda-store-ui release including such patch