Description
The Regen stubs workflow (.github/workflows/regen-stubs.yml) has failed on every decree-released dispatch (2026-06-19, 2026-06-21, 2026-06-30). It fails at npm run generate with sh: 1: buf: not found (exit 127) — buf is not installed in the job. A second gap sits behind it: the workflow never checks out opendecree/decree, where the protos live, so buf generate would have no proto input even once buf is installed.
This is pre-existing and non-urgent: the decree v0.12.0-alpha.5 release changed no protos, so the committed stubs are not stale. The break only matters on the next actual proto change. A companion fix is tracked for the Python SDK.
Acceptance criteria
Description
The
Regen stubsworkflow (.github/workflows/regen-stubs.yml) has failed on everydecree-releaseddispatch (2026-06-19, 2026-06-21, 2026-06-30). It fails atnpm run generatewithsh: 1: buf: not found(exit 127) —bufis not installed in the job. A second gap sits behind it: the workflow never checks outopendecree/decree, where the protos live, sobuf generatewould have no proto input even once buf is installed.This is pre-existing and non-urgent: the decree v0.12.0-alpha.5 release changed no protos, so the committed stubs are not stale. The break only matters on the next actual proto change. A companion fix is tracked for the Python SDK.
Acceptance criteria
bufis installed in the job (for example, viabufbuild/buf-setup-action).opendecree/decreesobuf generatehas its proto input.workflow_dispatchtrigger with a version input is added so the workflow can be tested without cutting a release.workflow_dispatchrun completes green: stubs regenerate,npm testpasses, and a pull request is opened (a no-op pull request is acceptable when protos are unchanged).