Skip to content

fix(ci): bump release-drafter to v7.2.1 to fix repo-only _extends#458

Open
adehad wants to merge 3 commits intoansible:mainfrom
adehad:fix/release-drafter-extends-bug
Open

fix(ci): bump release-drafter to v7.2.1 to fix repo-only _extends#458
adehad wants to merge 3 commits intoansible:mainfrom
adehad:fix/release-drafter-extends-bug

Conversation

@adehad
Copy link
Copy Markdown

@adehad adehad commented May 6, 2026

The pinned SHA (139054ae) corresponds to release-drafter v7.1.1, which broke the legacy _extends: org/repo syntax in v7.0.0. Consumers whose .github/release-drafter.yml uses _extends: ansible/team-devtools (without an explicit filepath) fail with:

    Unsupported file extension: .ansible/team-devtools.
    Supported extensions are: json, yml, yaml

(eg. https://github.com/pycontribs/jira/actions/runs/25213081718/job/73927583841)

release-drafter release-drafter/release-drafter#1577 (shipped in v7.2.0) restored support for the repo-only form. Bumping the pin to v7.2.1 (ec076381) unblocks all downstream repos that consume these reusable workflows.

The pinned SHA (139054ae) corresponds to release-drafter v7.1.1, which
broke the legacy `_extends: org/repo` syntax in v7.0.0. Consumers whose
.github/release-drafter.yml uses `_extends: ansible/team-devtools`
(without an explicit filepath) fail with:

    Unsupported file extension: .ansible/team-devtools.
    Supported extensions are: json, yml, yaml

release-drafter PR #1577 (shipped in v7.2.0) restored support for the
repo-only form. Bumping the pin to v7.2.1 (ec076381) unblocks all
downstream repos that consume these reusable workflows.

Refs: release-drafter/release-drafter#1577
@shatakshiiii
Copy link
Copy Markdown
Contributor

shatakshiiii commented May 7, 2026

Thanks for this PR @adehad

There is an error in tox -e lint due to token issue, we'll take a look at that and merge this pr ASAP!

@adehad
Copy link
Copy Markdown
Author

adehad commented May 7, 2026

No worries @shatakshiiii , I actually think the renovate branch would also fix the issue
I assume the token issue is because I am making the PR from a fork

Feel free to close, maybe I could have made an issue instead of a PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants