fix: generate release changelog from built ISO artifacts#714
Merged
Conversation
3alpha
approved these changes
Jun 11, 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
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.
Summary
CHANGELOG.mduses the ISO filenames produced by the build jobs instead of hardcoded Bookworm names.images/path prefix.echo -enrelease body with a heredoc for easier maintenance.Why
The release body was still assuming fixed
DAppNode-...bookworm...ISO names, while the workflow now renames generated artifacts with distro/version-specificDappnode-...-attended.isoandDappnode-...-unattended.isofilenames. Deriving the release content from the generated artifacts keeps GitHub release notes aligned with the files actually uploaded.Test plan
images/prefix.