Skip to content

feat: add release highlights generator agentic workflow#197

Merged
Mossaka merged 6 commits intomainfrom
copilot/add-release-highlights-generator
Jan 16, 2026
Merged

feat: add release highlights generator agentic workflow#197
Mossaka merged 6 commits intomainfrom
copilot/add-release-highlights-generator

Conversation

Copy link
Contributor

Copilot AI commented Jan 10, 2026

  • Analyze existing release workflows (release.yml and update-release-notes.md)
  • Combine Release Highlights Generator into the release pipeline
  • Convert release.yml to release.md agentic workflow format
  • Include jobs for building, signing, and releasing
  • Add steps to prepare release data for AI agent
  • Include prompt for AI agent to generate release highlights
  • Use safe-outputs to prepend highlights to release description
  • Compile the workflow with gh aw compile
  • Verify the compiled .lock.yml file is generated correctly
  • Run CodeQL security scan (no security issues found)
  • Add dry run option for testing

Dry Run Mode

The workflow now supports a dry_run input option when triggered manually via workflow_dispatch. In dry run mode:

  • Docker images are built but NOT pushed to the registry
  • Signing and SBOM attestation steps are skipped
  • Release notes are previewed in the logs but no release is created
  • AI agent step is skipped (no release to update)
  • All artifacts are still uploaded for inspection

This allows testing the full build pipeline without making any external changes.

Custom agent used: create-agentic-workflow
Design agentic workflows using GitHub Agentic Workflows (gh-aw) extension with interactive guidance on triggers, tools, and security best practices.

Original prompt

convert release pipeline into an agentic workflow. Keep the release process, but add a Release Highlights Generator agent to Generate an engaging release highlights summary for this repo and this release tag.

Custom agent used: create-agentic-workflow
Design agentic workflows using GitHub Agentic Workflows (gh-aw) extension with interactive guidance on triggers, tools, and security best practices.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Copilot AI changed the title [WIP] Convert release pipeline into an agentic workflow feat: add release highlights generator agentic workflow Jan 10, 2026
Copilot AI requested a review from Mossaka January 10, 2026 04:58
Copy link
Collaborator

@Mossaka Mossaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines 2 to 22
description: Generate an engaging release highlights summary for new releases
on:
release:
types: [published]
workflow_dispatch:
permissions:
contents: read
issues: read
pull-requests: read
tools:
github:
toolsets: [default]
bash:
- "git log:*"
- "git diff:*"
- "git tag:*"
- "git show:*"
safe-outputs:
update-release:
max: 1
timeout-minutes: 10
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This release highlights generator should be combined with the current release pipeline. Check out https://github.com/githubnext/gh-aw/blob/main/.github/workflows/release.md for inspiration

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Combined the release highlights generator with the release pipeline in commit 81002e8. The release.md now includes:

  • jobs: with the full build/release process
  • steps: to prepare release data for the agent
  • Prompt section for AI-generated highlights
  • update-release safe output to prepend highlights

The pattern now matches the gh-aw reference workflow.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot looks good to me can you add a dry run option to this workflow so that I can test it out?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added dry_run option in commit ac7eb3f. You can now test the workflow via manual dispatch with "Dry run mode" enabled. In dry run mode:

  • Docker images are built but NOT pushed
  • Signing/SBOM steps are skipped
  • Release notes are previewed in the logs but no release is created
  • AI agent step is skipped (no release to update)

All artifacts are still uploaded for inspection.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 13, 2026

Test Coverage Report

Metric Coverage Covered/Total
Lines 77.19% 1300/1684
Statements 77.27% 1333/1725
Functions 77.17% 142/184
Branches 69.76% 450/645
Coverage Thresholds

The project has the following coverage thresholds configured:

  • Lines: 38%
  • Statements: 38%
  • Functions: 35%
  • Branches: 30%

Coverage report generated by `npm run test:coverage`

@github-actions
Copy link
Contributor

💥 WHOOSH! Smoke Claude springs into action on this pull request! [Panel 1 begins...]

@github-actions
Copy link
Contributor

📰 BREAKING: Smoke Copilot is now investigating this pull request. Sources say the story is developing...

@github-actions
Copy link
Contributor

Smoke Test Results

Last 2 merged PRs:

Test Results:

  • ✅ GitHub MCP Testing
  • ✅ File Writing Testing
  • ✅ Bash Tool Testing

Overall Status: PASS

📰 BREAKING: Report filed by Smoke Copilot fer issue #197 🗺️

@github-actions
Copy link
Contributor

Smoke Test Results (Claude Engine)

Last 2 merged PRs:

Test Results:

  • ✅ GitHub MCP: Read PR list
  • ✅ File Write: Created /tmp/gh-aw/agent/smoke-test-claude-21050172371.txt
  • ✅ Bash Tool: Verified file content
  • ❌ Playwright MCP: Connection errors (ERR_TUNNEL_CONNECTION_FAILED)

Overall Status: FAIL (Playwright connectivity issues)

💥 [THE END] — Illustrated by Smoke Claude fer issue #197 🗺️

Mossaka added a commit that referenced this pull request Jan 15, 2026
GitHub's default CodeQL setup was attempting to analyze Python code,
but this repository only contains JavaScript/TypeScript and GitHub
Actions. The false detection was caused by a Python file in
node_modules (flatted/python/flatted.py).

This explicit workflow:
- Only analyzes javascript-typescript and actions languages
- Replaces the default setup with controlled configuration
- Prevents "no source code found" errors for Python
- Runs on PR, push to main, weekly schedule, and manual dispatch

Fixes the CodeQL failure in PR #197.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@github-actions
Copy link
Contributor

💥 WHOOSH! Smoke Claude springs into action on this pull request! [Panel 1 begins...]

@github-actions
Copy link
Contributor

📰 BREAKING: Smoke Copilot is now investigating this pull request. Sources say the story is developing...

@github-actions
Copy link
Contributor

Smoke Test Results

GitHub MCP:#225, #224
File Writing: ✅ Created test file
Bash Tool: ✅ Verified file

Status: PASS

📰 BREAKING: Report filed by Smoke Copilot fer issue #197 🗺️

@github-actions
Copy link
Contributor

Smoke Test Results (Claude Engine)

Last 2 merged PRs:

Test Results:

  • ✅ GitHub MCP: Retrieved PRs successfully
  • ✅ File Writing: Created test file with timestamp
  • ✅ Bash Tool: Verified file creation
  • ❌ Playwright MCP: Page loaded but assets failed (ERR_TUNNEL_CONNECTION_FAILED)

Overall Status: FAIL (Playwright connectivity issue)

💥 [THE END] — Illustrated by Smoke Claude fer issue #197 🗺️

Copilot AI and others added 6 commits January 16, 2026 00:03
Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>
Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>
Co-authored-by: Mossaka <5447827+Mossaka@users.noreply.github.com>
Adds a validation step that checks package.json version matches the git tag
version before building. This prevents the issue where a tag is created on
a commit with the wrong version number, which caused the v0.9.0 release to
initially fail smoke tests.

The validation step provides clear error messages and remediation steps when
a mismatch is detected.

Resolves the root cause of workflow run 21004691307 failure.
GitHub's default CodeQL setup was attempting to analyze Python code,
but this repository only contains JavaScript/TypeScript and GitHub
Actions. The false detection was caused by a Python file in
node_modules (flatted/python/flatted.py).

This explicit workflow:
- Only analyzes javascript-typescript and actions languages
- Replaces the default setup with controlled configuration
- Prevents "no source code found" errors for Python
- Runs on PR, push to main, weekly schedule, and manual dispatch

Fixes the CodeQL failure in PR #197.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@Mossaka Mossaka force-pushed the copilot/add-release-highlights-generator branch from 9dd0757 to 5ac3a47 Compare January 16, 2026 00:03
@github-actions
Copy link
Contributor

📰 BREAKING: Smoke Copilot is now investigating this pull request. Sources say the story is developing...

@github-actions
Copy link
Contributor

github-actions bot commented Jan 16, 2026

💫 TO BE CONTINUED... Smoke Claude failed! Our hero faces unexpected challenges...

@github-actions
Copy link
Contributor

Smoke Test Results

Last 2 Merged PRs:

Test Results:

  • ✅ GitHub MCP - Retrieved PR data
  • ✅ File Writing - Created test file successfully
  • ✅ Bash Tool - Verified file contents

Overall Status: PASS

📰 BREAKING: Report filed by Smoke Copilot fer issue #197 🗺️

@Mossaka Mossaka merged commit 33acf81 into main Jan 16, 2026
46 of 50 checks passed
@Mossaka Mossaka deleted the copilot/add-release-highlights-generator branch January 16, 2026 00:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants