Enable Release Drafter if needed

[basil]

If a plugin is using automated release, then any Release Drafter configuration should be deleted as explained here. But if the plugin is not using automated release and missing a Release Drafter configuration, it should be added to .github/release-drafter.yml and .github/workflows/release-drafter.yml as per the archetype:

• https://github.com/jenkinsci/archetypes/blob/7a9f24981d3c1993e47e540bb26d21f1f4469ce7/common-files/.github/release-drafter.yml
• https://github.com/jenkinsci/archetypes/blob/7a9f24981d3c1993e47e540bb26d21f1f4469ce7/common-files/.github/workflows/release-drafter.yml

The above configuration is for plugins with two digits in their version number. For plugins with three digits (SemVer-style), the following configuration should be used instead:

_extends: .github
name-template: $NEXT_PATCH_VERSION
tag-template: ${artifactId}-$NEXT_PATCH_VERSION
version-template: $MAJOR.$MINOR.$PATCH

[sghill]

What's the best way to tell if a plugin is using automated release @basil?

I'm thinking it involves checking for the presence of the cd.yaml workflow and cd.enabled: true in jenkins-infra/repository-permissions-updater

[basil]

Yes exactly, a plugin has automated release enabled if it has the maven-cd workflow in .github/workflows.