Skip to content

fix(ci): use workflow_dispatch for polish release notes #533

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TabishB merged 2 commits into from
Jan 20, 2026
Merged

fix(ci): use workflow_dispatch for polish release notes #533

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c836bc9
fix(ci): use workflow_dispatch for polish release notes
TabishB Jan 20, 2026
53f6b98
fix: get tag from package.json instead of gh release list
TabishB Jan 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 3 additions & 9 deletions .github/workflows/polish-release-notes.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,8 @@
name: Polish Release Notes

# Automatically polish release notes when a release is published.
# Also supports manual trigger as a fallback.
#
# Note: The Claude Code Action works with any GitHub event when using the
# `prompt` parameter for custom automations. If release triggers stop working,
# check https://github.com/anthropics/claude-code-action for updates.
# Uses Claude to transform raw changelog into polished release notes.
# Triggered automatically by release-prepare after publishing, or manually.
on:
release:
types: [published]
workflow_dispatch:
inputs:
tag_name:
Expand All @@ -17,7 +11,7 @@ on:
type: string

env:
TAG_NAME: ${{ github.event.release.tag_name || inputs.tag_name }}
TAG_NAME: ${{ inputs.tag_name }}

permissions:
contents: write
Expand Down
12 changes: 12 additions & 0 deletions .github/workflows/release-prepare.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,7 @@ jobs:

# Opens/updates the Version Packages PR; publishes when the Version PR merges
- name: Create/Update Version PR
id: changesets
uses: changesets/action@v1
with:
title: 'chore(release): version packages'
Expand All @@ -57,3 +58,14 @@ jobs:
env:
GITHUB_TOKEN: ${{ steps.app-token.outputs.token }}
# npm authentication handled via OIDC trusted publishing (no token needed)

# Trigger release notes polishing after a release is published
- name: Polish release notes
if: steps.changesets.outputs.published == 'true'
env:
GH_TOKEN: ${{ steps.app-token.outputs.token }}
run: |
# Get version from package.json (just bumped by changesets)
TAG="v$(jq -r .version package.json)"
echo "Triggering polish workflow for $TAG"
gh workflow run polish-release-notes.yml -f tag_name="$TAG"
Copy link

@greptile-apps greptile-apps bot Jan 20, 2026

Choose a reason for hiding this comment

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

style: verify that gh release list --limit 1 returns the most recently published release - the command assumes chronological ordering (newest first)

Prompt To Fix With AI 
This is a comment left during a code review.
Path: .github/workflows/release-prepare.yml
Line: 71:71

Comment:
**style:** verify that `gh release list --limit 1` returns the most recently published release - the command assumes chronological ordering (newest first)

How can I resolve this? If you propose a fix, please make it concise.

Loading