Since we can't use the current automated release workflow on the 0.35.x branch due to recent changes, I added a manual version bump to this PR as well, and will push the release tag and publish crates locally once this merges.

Subscribe to Label Action

cc @cfallin, @fitzgen

@alexcrichton informs me that we can still use part of the automation here: the recent CI changes mean that the version bump is still manual, but I've added the special tag to the commit message so the crate upload and release tagging will still be automatic.

(To document it here, since it differs from our published point-release process here: the issue is that the workflow name changed. If we need another point release on 0.35.0, we need to manually version-bump with scripts/publish.rs running ./publish bump-patch and commit that, then add the [automatically-tag-and-release-this-commit] at the end of the commit, then make a PR against the stable branch and merge it once approved/green-CI. This semi-manual process is only needed to do a point release on 0.35.0; a point release on 0.36.0 or later will work fine with the workflow trigger as described in our published docs. Also, note that the "security release" checklist in that doc is different and has always been manual, because of CI limitations in the private fork.)