Charlie Marsh 4634560c80 Ensure release tagging has access to repo clone (#5240) ...

## Summary

The [release
failed](https://github.com/astral-sh/ruff/actions/runs/5329733171/jobs/9656004063),
but late enough that I was able to do the remaining steps manually. The
issue here is that the tagging step requires that we clone the repo. I
split the upload (to PyPI), tagging (in Git), and publishing (to GitHub
Releases) phases into their own steps, since they need different
resources + permissions anyway.

2023-06-21 10:24:33 -04:00

..

benchmark.yaml

Small CI improvements (#4953)

2023-06-09 09:03:34 +02:00

ci.yaml

Make the release workflow more resilient (#4728)

2023-06-20 18:33:09 +00:00

docs.yaml

Only run the playground release job on release (#4636)

2023-05-24 11:48:36 -04:00

flake8-to-ruff.yaml

Small CI improvements (#4953)

2023-06-09 09:03:34 +02:00

playground.yaml

Only run the playground release job on release (#4636)

2023-05-24 11:48:36 -04:00

pr-comment.yaml

Small CI improvements (#4953)

2023-06-09 09:03:34 +02:00

release.yaml

Ensure release tagging has access to repo clone (#5240)

2023-06-21 10:24:33 -04:00