Skip to content

feat: add lightweight workflow run steps - #88

Merged
kj-podonos merged 1 commit into
mainfrom
codex/pod-617-lightweight-workflow-steps
Jul 16, 2026
Merged

feat: add lightweight workflow run steps#88
kj-podonos merged 1 commit into
mainfrom
codex/pod-617-lightweight-workflow-steps

Conversation

@kj-podonos

Copy link
Copy Markdown
Contributor

Summary

  • regenerate the public SDK from backend contract 25958e9a
  • expose lightweight workflow-run steps on sync, async, and raw clients
  • add include_result, node_type, and node_id to workflows.runs.steps
  • update the CLI, generated reference, manifest, and contract coverage

Compatibility

Workflow-step results are lightweight by default. Pass include_result=true to retrieve full result payloads; node_type and node_id filters can be combined.

The generated response model accepts older backend payloads that do not yet contain has_result or active_ports, which permits the required SDK-first rollout.

This feat: commit prepares the pre-1.0 minor release 0.12.0 through release-please. No version file was manually edited.

Validation

  • fern check
  • make lint
  • make typecheck
  • make test
  • make build
  • focused sync, async, raw, CLI, manifest, legacy-payload, and distribution contract suites
  • independent spec and quality review: approved with no findings

Dependencies

Required eventual release order: SDK 0.12.0, backend, then frontend.

No merge, publish, release, deploy, or Sentry mutation is part of this PR.

@kj-podonos kj-podonos self-assigned this Jul 15, 2026
@kj-podonos

Copy link
Copy Markdown
Contributor Author

@codex this PR is out of date and has rebase conflicts against main now that donut-be #444 has merged (the OpenAPI spec changed). Please rebase codex/pod-617-lightweight-workflow-steps onto latest main and regenerate the Fern SDK against the updated spec — do not hand-merge. All conflicts are in generated artifacts:

  • .spec-sha
  • src/onepin/.fern/metadata.json
  • src/onepin/reference.md
  • src/onepin/voices/raw_client.py
  • src/onepin/workflows/client.py
  • src/onepin/workflows/raw_client.py

Keep the new lightweight workflow run steps method + the optional has_result/active_ports fields (SDK 0.12.0 must parse older-backend responses). Then force-push the rebased branch.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex couldn't complete this request. Try again later.

@kj-podonos
kj-podonos force-pushed the codex/pod-617-lightweight-workflow-steps branch from c2332f8 to aa6652a Compare July 16, 2026 05:18
The lightweight run-steps SDK method is already synced on main (#89). This adds
the hand-rolled CLI options for it — `--include-result`, `--node-type`,
`--node-id` on `workflows runs steps` — plus SDK contract and CLI dispatch tests
covering the new filters. Generated SDK is left untouched (matches main).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@kj-podonos
kj-podonos force-pushed the codex/pod-617-lightweight-workflow-steps branch from aa6652a to 8598a44 Compare July 16, 2026 06:04
@kj-podonos
kj-podonos merged commit 69b22e4 into main Jul 16, 2026
22 checks passed
@kj-podonos
kj-podonos deleted the codex/pod-617-lightweight-workflow-steps branch July 16, 2026 06:09
kj-podonos added a commit that referenced this pull request Jul 20, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.12.0](v0.11.0...v0.12.0)
(2026-07-16)


### Features

* add lightweight workflow run steps
([#88](#88))
([69b22e4](69b22e4))
* sync SDK to OnePin API v0.41.82
([#85](#85))
([c967181](c967181))
* sync SDK to OnePin API v0.41.83
([#89](#89))
([9603910](9603910))


### Bug Fixes

* **cli:** support run-steps SDK method migration
([#87](#87))
([968747c](968747c))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
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.

1 participant