Skip to content

Playbooks: document choosing the Python SDK version (v4 or v5) - #482

Merged
maximelb merged 1 commit into
masterfrom
playbook-sdk-v5
Oct 4, 2026
Merged

maximelb merged 1 commit into
masterfrom
playbook-sdk-v5

Conversation

@maximelb

@maximelb maximelb commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

Playbooks can now run on the Python SDK v5, so this page no longer says v5 is unsupported.

  • Replaces the "v4 only" warning with a note pointing to a new Python SDK version section.
  • The new section covers the optional sdk_version field (absent, empty or "4" = v4; "5" = v5), what sdk is under each version, v5 specifics (JSON-serializable return value, is_interactive is v4-only, background work stops when playbook() returns) and a v5 example playbook.
  • Adds a v5 version of the "call a playbook from Python" example, a v5 Infrastructure as Code example, and notes which packages exist for each SDK.

The v5 example playbook and the v5 calling example were run against a live organization before writing them here. mkdocs build --strict and markdownlint-cli2 pass locally.

The web app's SDK selector mentioned on the page ships with the next web app release.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@maximelb

maximelb commented Oct 4, 2026

Copy link
Copy Markdown
Contributor Author

/lc-review

@maximelb
maximelb merged commit 5d9236c into master Oct 4, 2026
7 checks passed
@maximelb
maximelb deleted the playbook-sdk-v5 branch October 4, 2026 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants