-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REL] - 2024.3.1 #755
Labels
Comments
conda-store release is available on PyPI |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Release details
Scheduled release date - 2024/03/22
Release captain responsible - @trallard @pavithraes
1. Pre-flight checks
block-release ⛔️
label2. Prepare the codebase for a new release
Create a new git branch for the release
git checkout -b release-2024.3.1
git clean -fxdq
Bump
conda-store
version inconda-store/conda-store/__init__.py
Bump
conda-store-server
version inconda-store-server/conda-store-server/__init__.py
Update the
conda-store-ui
version used inconda-store-server
conda-store-server/hatch_build.py
Update the CHANGELOG.md file with the new version, release date, and relevant changes1.
Check the version locally with
hatch version
Build and test locally
For
conda-store
andconda-store-server
:Make a release commit:
git commit -m 'REL - 2024.3.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
2024.3.1
Choose a Tag:
dropdown, type in the release name (e.g.,2024.3.1
) and click "Create new tag"Target:
dropdown, pin it to the release commit you've recently pushed.release
GitHub action job has completed successfully in the actions tab.conda-store
PyPI version is updatedconda-store-server
PyPI version is updatedmeta.yaml
orrecipe.yaml
and re-render the feedstock.Footnotes
If you wish, use
github-activity
to generate a Changelog, e.g.github-activity conda-incubator/conda-store --since 2023.9.1 --until 2023.10.1
. ↩ ↩2The text was updated successfully, but these errors were encountered: