Seed the release branch with the corrected discord-release-notify workflow and version baseline BEFORE the next master->release merge, so that merge announces v3.0.0 and the workflow bumps the patch (3.0.0 -> 3.0.1 -> ...) on every subsequent merge instead of repeating the same version. A direct push (not a pull_request) does not trigger the announce workflow, so this is safe to land here ahead of the merge. |
||
|---|---|---|
| .. | ||
| workflows | ||
| FUNDING.yml | ||