automation

This PR reverts #66 to use the new config approach instead of the deprecated config. I noticed in a recent run that there is now a deprecation warning logged due to our use of because we updated the release drafter action to 7.4.0. This version released the new config approach that was not available last time we were configuring this. If I understand the docs correctly, this change is also an improvement: currently, if a PR touches any of our it is not included in the relase notes, even if it touched a relevant file. The new config style should fix that.

Description This PR fixes the excludes made in https://github.com/withastro/automation/pull/65 and https://github.com/withastro/automation/commit/3e735d87bb9d4139dd14e88247c1d90d404f2d85. Turns out this was recently entirely refactored in the action but not yet released, so by checking the documentation on the default branch we were using invalid configuration options. This PR uses the option documented from the documentation: https://github.com/release-drafter/release-drafter/tree/v7.3.1

Description As a follow-up to this Discord discussion and to avoid workaround like this one, this PR adds a workflow to automatically generate a draft release when changes are merged to , similar to part of the process used in the repo. I did not add the workflow that creates or updates a major version tag, such as , to point at the latest release, as we want to encourage usage using a commit SHA with the corresponding version tag (e.g. ) inside the organization. I did not add any configuration regarding labels for as I don't think we would end up using them. The default version resolver strategy is and we can always update the release tag and title if needed before publishing the release. For the first release, we should manually remove the link as there is no previous tag to compare against. I guess the only remaining question would be what should be the first version number?