fix(release): emit CHANGELOG section as GitHub release body#143
Merged
saurabhjain1592 merged 2 commits intomainfrom Apr 19, 2026
Merged
fix(release): emit CHANGELOG section as GitHub release body#143saurabhjain1592 merged 2 commits intomainfrom
saurabhjain1592 merged 2 commits intomainfrom
Conversation
…ht validation The previous release workflow published a generic "install + see CHANGELOG" body for every tagged release. Anyone landing on the release page (from README links, registry listings that pull GitHub release descriptions, or blog posts citing the tag) had to click through to see what changed. Worse, a missing CHANGELOG section would still publish to the registry first and only fail at the GitHub release step — leaving a partial release with no release page and no retry path on the same version. Changes: - New preflight job runs FIRST with no dependencies. Validates the CHANGELOG.md section exists for the target version (awk extracts the section between "## [X.Y.Z]" and the next "## ["), fails loudly with an actionable error if missing, builds the final release body (install block + CHANGELOG content), and uploads it as an artifact. - Publish/release jobs now depend on preflight. Missing CHANGELOG section → preflight fails → zero side effects. No partial releases. - Final release body = install block prepended to the extracted CHANGELOG section, delivered via body_path from the artifact. - Pinned actions/upload-artifact and actions/download-artifact to SHAs matching the repo's SHA-pinning convention where present. Matches the pattern established in axonflow-openclaw-plugin#47.
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
1 participant
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
Mirrors axonflow-openclaw-plugin#47 (already merged, verified on v1.3.1 release — release page now carries the full CHANGELOG section inline).
Before this change, every tagged release produced a generic "install + see CHANGELOG.md for details" body. Anyone landing on the GitHub release page (from README links, registry listings that pull GitHub release descriptions, or external citations) had to click through to see what changed. Worse, a missing CHANGELOG section would still publish to the registry first and only fail at the GitHub release step — leaving a partial release with no release page and no retry path on the same version.
Changes
preflightjob runs FIRST with no dependencies. Validates the CHANGELOG.md section exists for the target version (awk extracts the section between## [X.Y.Z]and the next## [), fails loudly with an actionable error if missing, builds the final release body (install block + CHANGELOG content), and uploads as artifact.body_pathfrom the artifact.actions/upload-artifactandactions/download-artifactto match repo convention.Test plan
yaml.safe_load)