Add post-agent release job to comment on PRs included in each release#41834
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
pelikhan
June 27, 2026 03:25
View session
pelikhan
approved these changes
Jun 27, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the release workflow to post a standardized “included in release” comment on every PR merged between the previous and current release, implemented as a dedicated post-agent job so PR notifications are decoupled from release-note generation.
Changes:
- Added a new
comment_release_prsjob to compute the release window and comment on merged PRs, with a per-release marker to prevent duplicate comments on reruns. - Wired workflow/job dependencies so the new job runs after
agentand consumesrelease_id+release_tagoutputs. - Regenerated the compiled
.lock.ymlworkflow to include the new job and updated dependencies.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/release.md |
Adds the comment_release_prs job (github-script) to search merged PRs in the release window and comment with a de-dupe marker. |
.github/workflows/release.lock.yml |
Regenerated compiled workflow including the new job and updated conclusion dependencies. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Low
Comment on lines
+732
to
+738
| const releaseTag = process.env.RELEASE_TAG; | ||
| const releaseId = Number(process.env.RELEASE_ID); | ||
|
|
||
| if (!releaseTag || Number.isNaN(releaseId)) { | ||
| core.setFailed(`Missing or invalid release context: RELEASE_TAG=${releaseTag}, RELEASE_ID=${process.env.RELEASE_ID}`); | ||
| return; | ||
| } |
Contributor
|
🎉 This pull request is included in a new release. Release: |
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.
The release workflow now posts a release notification comment on each PR merged into the released window. This is implemented as a dedicated job that runs after
agent, so release-note generation and PR notifications are decoupled.What changed
comment_release_prsto/home/runner/work/gh-aw/gh-aw/.github/workflows/release.md.agentand consumeconfig+releaseoutputs (release_tag,release_id).PR inclusion logic
release_id.previousRelease.published_at..currentRelease.published_at.Commenting behavior
<!-- gh-aw-release:<tag> -->) to avoid duplicate comments on reruns.Compiled workflow output
/home/runner/work/gh-aw/gh-aw/.github/workflows/release.lock.ymlto include the new job.