Prepare release: 1.0.2

[github-actions]

⚡ Merging this PR will automatically create a GitHub Release & publish the package ⚡

This PR was created by the Release stage 1 - create release PR workflow, triggered by @hjoliver

Tests:

• Tests last run on master:
• ✔️ Build check passed - see the workflow run (number 11) for more info

Checklist:

• Milestone complete?
  ⚠️ Couldn't find milestone matching 1.0.2
• Changelog up-to-date?
  • Examine pull requests made since the last release
  • "Released on" date updated? ✔️ 2022-05-19

Next steps:

• @hjoliver should request 1 or 2 reviews
• If any further changes are needed, push to this PR branch
• After merging, the bot will comment below with a link to the release (if not, look at the PR checks tab)

[codecov-commenter]

Codecov Report

Merging #351 (820845f) into master (d808078) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #351   +/-   ##
=======================================
  Coverage   78.68%   78.68%           
=======================================
  Files          11       11           
  Lines        1065     1065           
  Branches      206      206           
=======================================
  Hits          838      838           
  Misses        191      191           
  Partials       36       36           

Impacted Files	Coverage Δ
cylc/uiserver/__init__.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d808078...820845f. Read the comment docs.

[hjoliver]

Note I updated the UI on this PR branch (By copying the contents of cylc-ui/dist from a local build).

[hjoliver]

In setup.cfg:

   cylc-flow==8.0rc3.*  # the .* permits dev versions 

I presume that's OK for the release.

[oliver-sanders]

Note I updated the UI on this PR branch (By copying the contents of cylc-ui/dist from a local build).

Sorry, my bad, the release instructions weren't too clear on this. The plan is:

1. Release the UI.
2. Use the GH action to bump the UI version (uses the official release build)
3. Kick off the release process

cylc/cylc-admin#153 (comment)

No problem, no need to close this PR, suggest:

1. Revert the UI update commit.
2. Release the UI.
3. Update the UIS UI version (on master).
4. Rebase this PR.

[oliver-sanders]

I presume that's OK for the release.

Yep, this permits maintenance releases whilst keeping the Cylc system components tightly coupled.

[hjoliver]

A-ha, makes sense! (how the UI is updated).

I've removed that commit on this branch.

[MetRonnie]

I have run the GH workflow to update the bundled UI : #354

@hjoliver All that's left is to rebase this branch onto master (and possibly update the changelog date seeing as this will probably go on into tomorrow UTC)

[hjoliver]

Hmm, we didn't have a pending-release heading in the change log prior to this, so the action changed the 1.0.1 heading. Doing a little manual surgery...

[hjoliver]

@MetRonnie - this should be good to go now (rebased, change log tweaked).

[github-actions]

✔️ success

Next steps for @hjoliver:

• view/edit the GitHub release description as appropriate
• ✔️ Milestone automatically closed

---

Comment created by workflow: Release stage 2 - auto publish, run: 16