This now requires a separate manually triggered `publish` workflow to be run after the release completes in order to transition the release to the `published` state. Practically today this only means that the release will be published to the macOS auto-updater, but in the future we could add additional steps such as creating a GH release or some other notifications. Importantly, this lets us verify the release in the uploaded location before general users are notified of the update. |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| dependabot.yml | ||