Hi there,
In #768 we added the Renovate changelog annotation to the Dockerfile
Renovate now correctly detects the changelog location and links it to the PRs — however, because of the structure of the upstream changelog, the PR body ends up displaying an empty changelog section instead of the actual release notes.
Every release entry in your changelog.md looks like this wh
## [v1.82.0](https://github.com/DialmasterOrg/Youtarr/releases/tag/v1.82.0) - 2026-09-08
## [1.82.0](https://github.com/DialmasterOrg/Youtarr/compare/vv1.81.1...v1.82.0) (2026-09-08)
### Features
Renovate's changelog extractor scans for a heading that matches the released version and takes everything between that heading and the next heading of the same level. For v1.82.0, it matches the first heading (## v1.82.0 - 2026-09-08) — but the very next line is already another ## heading, so the extracted body is empty. The actual release notes live under the second heading.
Additionally, the second heading's compare links contain a typo — a doubled v:
https://github.com/DialmasterOrg/Youtarr/compare/vv1.81.1...v1.82.0
Expected Behavior
One heading per release with the release notes (Features / Bug Fixes / …) directly beneath it
Thank you again for sharing this software with us!!
Hi there,
In #768 we added the Renovate changelog annotation to the Dockerfile
Renovate now correctly detects the changelog location and links it to the PRs — however, because of the structure of the upstream changelog, the PR body ends up displaying an empty changelog section instead of the actual release notes.
Every release entry in your changelog.md looks like this wh
Renovate's changelog extractor scans for a heading that matches the released version and takes everything between that heading and the next heading of the same level. For v1.82.0, it matches the first heading (## v1.82.0 - 2026-09-08) — but the very next line is already another ## heading, so the extracted body is empty. The actual release notes live under the second heading.
Additionally, the second heading's compare links contain a typo — a doubled v:
Expected Behavior
One heading per release with the release notes (Features / Bug Fixes / …) directly beneath it
Thank you again for sharing this software with us!!