e-volv

Docs playbook

SDKRegeneration

On each release, regenerates the client SDK from the OpenAPI document and opens a follow-up PR with the new client and migration notes.

When a release is published, regenerates the client SDK from the release's OpenAPI document, runs the SDK's own build and tests, and opens a pull request against the SDK repository with the regenerated client, a changelog derived from the spec diff, and migration notes for any breaking changes. The PR is held for human review and is not merged automatically.

Identifier
sdk-regeneration
Version
1.0.0
Steps
3
Triggers
1
  • sdk
  • openapi
  • release
  • regeneration
  • client
  • automated

When it runs

Releaserelease.published
Settle delay
10s after the event

Only when all hold

  • release.draft not equals true
  • actor.username not contains [bot]

The pipeline

The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.

React Flow
  1. 01
    Release Publishedtrigger

    The event that starts the run.

  2. 02
    Clone SDK Repository ⚠️ SET YOUR REPOgit.clone

    Shallow-clones the repository at the right ref.

  3. 03
    Regenerate SDKagent.run

    One agent works the task with its toolkit.

The agent

SDK Regenerator

Base type
Senior Developer
Temperature
0.2
Max iterations
50
Tools
7

Git provider · 3

  • create_branchCreate Branch · write
  • create_or_update_fileCreate or Update File · write
  • create_pull_requestCreate Pull Request · write

Filesystem · 2

  • read_fileRead File · read
  • edit_fileEdit File · write

Terminal · 1

  • run_terminal_cmdRun Terminal Command · write

Status · 1

  • update_statusUpdate Status · write