Ensure all Cylc components are pinned to the correct version of cylc-flow.
Trigger releases via GitHub actions.
[x] metomi-isodatetime
[x] cylc-flow (bump metomi-isodatetime if required)
[x] cylc-ui
[x] cylc-uiserver (update the ui version before releasing)
[x] metomi-rose (bump metomi-isodatetime if required)
[x] cylc-rose
Forge (check dependencies match):
Pull requests will be automatically opened on the conda-forge feedstocks
after the pypi releases.
If not, create a new branch, change the version, reset the build number and
update the hash from the PyPi website.
Finally trigger a rerender in a comment.
Ensure dependencies are up to date and follow instructions on the PR. Some
repos may maintain a list of conda dependencies locally.
[x] cylc-flow
[x] cylc-ui
[x] cylc-uiserver
[x] metomi-rose
[x] cylc-rose
It make take a couple of hours for a release to become available.
Use conda search <package> to determine when it's ready.
Misc (after the above has been completed):
cylc-doc
[x] bump instersphinx versions if required
[x] review installation instructions
[x] deploy (run the "deploy" workflow on GitHub Actions) (can be re-deployed later if necessary)
metomi-rose
[x] build & deploy documentation (manual process ATM)
[x] discourse post
Metadata:
Update project versions to the next milestone
AND pin downstream components to the next cylc-flow dev release.
Release Progress
Issue to track the coordinated release of multiple Cylc components.
Required for all minor releases of cylc-flow.
See the release docs for first time instructions and more info.
Prep:
Non-bumpable PRs
Milestones for release:
PyPi / GitHub releases:
Forge (check dependencies match):
Misc (after the above has been completed):
Metadata:
Finally: