Repository navigation
Prepare release 11.0.1.1 #632
Description
- Create dedicated Git branch
- Update the CHANGELOG.md file with the proper version and release date on this branch
- Update the version for Pip and dev Conda package
- in the
khiops/__init__.pyfile (for the Pip package) - in the
packaging/conda/meta.yamlfile
- in the
[ ] Updatekhiops-coredependency version:[ ] in thepyproject.tomlfile[ ] in thepackaging/conda/meta.yamlfile
- Launch expensive tests manually on this branch
- Create PR on this branch
- Let the Pip package workflow launch automatically on this branch to see there is no error
- Let the Api-docs workflow launch automatically on this branch to see there is no error:
- Inspect workflow execution log to see there are no build warnings
- Download and inspect the generated docs locally to see there is no apparent issue
- If everything goes well after these stages, ask for review on the PR
- If the review is OK, then merge the PR branch into the
mainbranch - Tag the
mainbranch with the 11.0.1.1 Git tag - Let the Pip package publishing workflow launch automatically on the 11.0.1.1 Git tag, to trigger GitHub pre-release creation
- Manually launch the Api-docs workflow on the 11.0.1.1 tag and check there are no build warnings
- After the success of these stages, manually launch the Pip package publishing workflow on the 11.0.1.1 Git tag, to publish the package on Test.PyPI
- Manually install the
khiopspackage from the test.pypi repository into a local virtual environment and perform some tests:- That the installation went well, with all dependencies correctly installed in the virtual environment
- That the
import khiops.core as kh; kh.get_runner().print_status()works well inside a Python console launched in the virtual environment
- If all the above tests are successful, then manually launch the Pip package publishing workflow on the 11.0.1.1 Git tag, to publish the package on the PyPI repository
- Publish the release on the
conda-forgeConda channel:- Synchronise the personal fork of the
khiops-feedstockGit repository in theconda-forgegroup on GitHub (https://github.com/conda-forge/khiops-feedstock/) with the upstream - On the personal fork of the Khiops feedstock, create branch based on the
mainbranch - On that branch, update the Conda recipe: bump the version and update the SHA256 of the package tarball
- Create PR onto the upstream repository on
conda-forge - Ask to re-render on that PR
- Ask for review of that PR, then, after approval, merge it into upstream
- Check that the package is successfully published on
conda-forge - If a bot creates a PR on
khiops-feedstockafter detecting the new release on PyPI, just ignore and close it
- Synchronise the personal fork of the
- Test the package published on
conda-forgevia thetest-conda-forge-package.ymlworkflow. If there are errors, go back to the previous step, update thekhiops-feedstockrepository onconda-forgewith the fix, bump the recipe build number and publish the package onconda-forge. - Copy the CHANGELOG.md update regarding the 11.0.1.1 release to the 11.0.1.1 GitHub pre-release description
- Turn the 11.0.1.1 GitHub pre-release into a release and set it as "latest"
- Update the website
- Create a new PR in the khiops-doc project to update the khiops-python version
- Merge this PR and launch the website workflow
- Update the khiops-python version in docker images
- Create a new PR in the khiops-docker project, merge it and tag a new version
- Create a new PR in the khiops-notebook project, merge it and tag a new version
Activity