[REL] - 2024.11.1

[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.11.1

  • Prepare the branch with git clean -fxdq

• Bump the version in the package.json file

• [Optional] Update the conda-store-ui version used in the extension:

  yarn upgrade @conda-store/conda-store-ui@<version>

• 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 (see the RELEASE.md file for more details)

• Make a release commit: git commit -m 'REL - 2024.11.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.11.1
  • In the Choose a Tag: dropdown, type in the release name (e.g., 2024.11.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 been completed successfully in the actions tab.
  • The jupyterlab-conda-store PyPI version is updated
• Celebrate, you're done! 🎉

Footnotes

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

[soapy1]

depends on #71