Bump cylc-flow version

[MetRonnie]

If the next uiserver release is a minor rather than maintenance one, then doesn't it need to have a dependency on the next cylc-flow minor release?

Requirements check-list

• I have read CONTRIBUTING.md and added my name as a Code Contributor.
• Contains logically grouped changes (else tidy your branch by rebase).
• Does not contain off-topic changes (use other PRs for other changes).
• Any dependency changes applied to setup.cfg.
• Does not need tests
• No change log entry required
• No documentation update required.

[hjoliver]

If the next uiserver release is a minor rather than maintenance one, then doesn't it need to have a dependency on the next cylc-flow minor release?

But I suppose we can't be sure yet that the next UIS release will not be a maintenance release (we might find a bug requiring a quick fix...).

[MetRonnie]

I say we branch off the 1.1.0 tag in that case

[oliver-sanders]

If the next uiserver release is a minor rather than maintenance one, then doesn't it need to have a dependency on the next cylc-flow minor release?

Yes, this is on the cylc-admin issue template (metadata section) but got missed this time around. The same also applies to cylc-rose.

cylc/cylc-admin#157

[oliver-sanders]

Note that the tests are run against the cylc-flow master branch. For maintenance releases we would need to modify the test workflow to either install from a selected branch. Installing the released version is probably preferable.

[MetRonnie]

Actually as there's currently the dependency on cylc-flow==8.0.*, it's currently installing cylc-flow master, then uninstalling and replacing with 8.0.1

cylc-uiserver/.github/workflows/test.yml

Lines 33 to 36 in 5286d48

	- name: Install cylc-uiserver & dependencies
	run: |
	pip install git+https://github.com/cylc/cylc-flow@master
	pip install -e .[all]