Skip to content

Integrate Oz changelog skill into create_release workflow#10832

Draft
vikvang wants to merge 1 commit into
masterfrom
oz/changelog-release-workflow
Draft

Integrate Oz changelog skill into create_release workflow#10832
vikvang wants to merge 1 commit into
masterfrom
oz/changelog-release-workflow

Conversation

@vikvang
Copy link
Copy Markdown
Contributor

@vikvang vikvang commented May 13, 2026

Description

Replace the warpdotdev/generate-changelog GitHub Action in the generate_changelogs job with the Oz changelog-draft skill (oz-agent-action). This makes the release changelog generation AI-powered, using the same skill that was landed in #10280.

What changed

  • SKILL.md: Step 8 now produces a third output file changelog-release.json with the {newFeatures, improvements, bugFixes, images, oz_updates} schema expected by the Slack payload builder and in-app changelog.json steps.
  • create_release.yml: The generate_changelogs job now:
    1. Runs oz-agent-action with a prompt to follow the changelog-draft skill workflow
    2. A bridge step reads changelog-release.json and sets outputs.changelog so all downstream steps (Slack post, GCS upload) work unchanged
    3. Fixes .image to .images key in the changelog.json builder for schema consistency

How it works

The Oz agent runs the full skill workflow (fetch PRs, classify contributors, extract feature flags, classify unmarked PRs, assemble draft) and writes three files:

  • changelog-draft.md — human-reviewable markdown
  • changelog-draft.json — machine-readable audit artifact
  • changelog-release.json — release-pipeline-compatible JSON (new)

The bridge step loads changelog-release.json into steps.generate_changelog.outputs.changelog, maintaining the same interface the downstream Slack and GCS steps expect.

Linked Issue

Testing

  • Validated YAML structure (1788 lines, all key references intact)

  • Generated a real changelog-release.json from the latest stable release range (v0.2026.05.06 → v0.2026.05.13): 2 new features, 10 improvements, 27 bug fixes, 1 image

  • Ran the exact downstream jq transforms (Slack payload builder + changelog.json builder) against the generated JSON — all produce valid output

  • Full end-to-end test will occur on the next release cut

  • I have manually tested my changes locally with ./script/run

Agent Mode

  • Warp Agent Mode - This PR was created via Warp's AI Agent Mode

Co-Authored-By: Oz oz-agent@warp.dev

Replace the warpdotdev/generate-changelog action in the generate_changelogs
job with oz-agent-action, which invokes the changelog-draft skill to produce
a release-compatible JSON artifact (changelog-release.json).

Changes:
- SKILL.md Step 8: add third output file (changelog-release.json) with the
  {newFeatures, improvements, bugFixes, images, oz_updates} schema consumed
  by the Slack payload builder and in-app changelog.json steps.
- create_release.yml: replace GitHub App token + generate-changelog steps
  with oz-agent-action + a bridge step that reads changelog-release.json
  and exposes it as outputs.changelog for downstream compatibility.
- Fix .image -> .images key in the changelog.json builder step to match
  the new schema.

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label May 13, 2026
@vikvang vikvang requested a review from danielpeng2 May 13, 2026 19:09
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.

1 participant