Fix the release-drafter config so the job stops failing on every merge - #11
Merged
Conversation
The Release Drafter job has failed on every merge to main with `"template" is required`, and it has never worked in this repository. The config was four lines, and the load-bearing one was `_extends: .github`. That is release-drafter's inheritance directive: it reads a base config from a repo named `.github` in the SAME organization. The file was copied from the Jenkins plugin template, where jenkinsci/.github exists and supplies the required `template` key. controlplane-com/.github does not exist -- the API returns 404 -- so nothing was inherited. The failure output showed exactly that: every inherited field came back empty (name-template '', categories [], header '', footer ''). Only tag-template, which was set locally, had a value. This inlines a config instead of inheriting one, so the repo does not depend on an org-level repository that may never be created. Categories are trimmed to labels this repo plausibly uses rather than carrying the full Jenkins set, and the jenkinsci-specific replacers (JENKINS/JEP/HELPDESK issue links) are dropped because they point at trackers this project does not use. tag-template keeps the existing cpln-jenkins-plugin-$NEXT_MINOR_VERSION shape. That deliberately does not collide with the vX.Y.Z tags the image publish workflow pushes: it matches on 'v[0-9]*.[0-9]*.[0-9]*', which a cpln-jenkins-plugin-2.1 tag does not satisfy. Not addressed: release-drafter@v6 runs on Node 20, which GitHub is deprecating. That warning is emitted by the action itself and is unrelated to the config; it appears on passing runs too, and fixing it means waiting for an upstream release.
enk21
approved these changes
Aug 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release Drafterfails on every merge tomainwith"template" is required. It has never worked in this repository.Why
The config was four lines, and the load-bearing one was
_extends: .github.That is release-drafter's inheritance directive — it reads a base config from a repo named
.githubin the same organization. This file was copied from the Jenkins plugin template, wherejenkinsci/.githubexists and supplies the requiredtemplatekey.controlplane-com/.githubdoes not exist (the API returns 404), so nothing was inherited.The failure output confirms it — every inherited field came back empty:
Only
tag-template, which was set locally, had a value.The fix
Inline the config rather than inherit it, so the repo doesn't depend on an org-level repository that may never be created. Verified by parsing the result:
_extendsis gone (it survives only inside an explanatory comment) andtemplateis present.Trimmed while inlining: categories reduced to labels this repo plausibly uses instead of the full Jenkins set, and the jenkinsci-specific replacers (
JENKINS-,JEP-,HELPDESK-issue links) dropped since they point at trackers this project doesn't use.The two tag schemes don't collide
Worth stating explicitly, since this repo now has two:
cpln-jenkins-plugin-$NEXT_MINOR_VERSIONpublish-image.ymlv2.0.0,v2.0.1, …The image workflow selects with
git tag -l 'v[0-9]*.[0-9]*.[0-9]*', which acpln-jenkins-plugin-2.1tag does not match. So drafted releases cannot perturb image versioning.Not addressed
release-drafter@v6runs on Node 20, which GitHub is deprecating. That warning comes from the action itself, not the config — it appears on passing runs too, and clearing it means waiting for an upstream release.🤖 Generated with Claude Code