Repository navigation
Plugin compatibility sweep at workflow v0.52.x (post-#617 godo removal) #656
Description
Tracking issue for plugin ecosystem compatibility against workflow v0.52.x (post-#617 godo removal cutover).
Current pin lag
| Plugin | Plugin version | minEngineVersion | go.mod pin |
|---|---|---|---|
| workflow-plugin-digitalocean | 0.12.0 | 0.51.2 | (current via #617 work) |
| workflow-plugin-audit-chain | 0.2.2 | 0.51.5 | likely current |
| workflow-plugin-payments | 0.4.3 | 0.51.2 | likely current |
| workflow-plugin-aws | 0.1.0 | missing | v0.19.2 |
| workflow-plugin-gcp | 0.1.0 | 0.3.56 | v0.19.2 |
| workflow-plugin-azure | 0.1.0 | 0.3.40 | v0.19.2 |
| workflow-plugin-tofu | 0.1.0 | 0.3.51 | v0.3.56 |
| workflow-plugin-github | 1.0.1 | 0.2.0 | v0.3.56 |
| workflow-plugin-gitlab | 1.0.2 | 0.19.0 | v0.19.0 |
| workflow-plugin-agent | 0.1.0 | missing | v0.10.2 |
| workflow-plugin-ci-generator | 0.1.0 | 0.19.0-alpha.5 | pseudo-version |
The bolded entries are >20 minor versions behind workflow v0.52.x.
Action matrix
| Issue class | Plugins affected | Action |
|---|---|---|
| Strict-contracts not migrated | aws, gcp, azure, agent, tofu, ci-generator, github (likely) | Mirror DO plugin v1.0.1 force-cutover (memory: project_strict_contracts_cutover_complete). Each plugin needs its own typed-IaC migration PR. AWS already has tracking issue workflow-plugin-aws#8. |
| minEngineVersion missing | aws, agent | Add to plugin.json |
| go.mod workflow pin stale | aws v0.19.2, gcp v0.19.2, azure v0.19.2, tofu v0.3.56, github v0.3.56, gitlab v0.19.0, agent v0.10.2 | Bump to workflow v0.52.x and re-run tests; fix any breakage |
| Feature gaps | aws (autoscaling_group — workflow-plugin-aws#9), digitalocean (step.iac_logs — #107, step.iac_scale — #108) | In-flight as of 2026-05-13 |
Recommended sequencing
- Now (in-flight): workflow-plugin-aws#9, workflow-plugin-digitalocean#107, workflow-plugin-digitalocean#108 — concrete gap closures.
- Next: AWS plugin typed-IaC migration (workflow-plugin-aws#8) — same pattern as DO v1.0.1. After this, workflow#653 Phase 1 unblocks.
- Then: GCP + Azure plugins typed-IaC migrations (file as new issues against each repo if not yet tracked).
- Finally: Engine pin sweep — bump every plugin's go.mod pin to workflow v0.52.x + retest.
Filing this as the umbrella tracker. Sub-issues against individual plugins per the action matrix.
Generated as part of the post-#617 autonomous compatibility audit. 🤖
Activity
docs: design revision 2 — incorporate adversarial review cycle 2 find…
plan: address adversarial-plan-review cycle 1 findings
intel352 commentedon May 16, 2026
Superseded by post-cloud-SDK plugin sweep landing at workflow v0.53.1; tracking 15 plugin PRs per docs/plans/2026-05-16-post-cloud-sdk-plugin-sweep.md. Original v0.52.x inventory in this issue is stale; the sweep picks up the actual current state. Closing-via-supersession when wave 1 + wave 2 complete.
intel352 commentedon May 16, 2026
Sweep complete 2026-05-16. All 15 lagging plugins bumped to workflow v0.53.1:
Plan: docs/plans/2026-05-16-post-cloud-sdk-plugin-sweep.md (sha256 e6545d28a798…). Pipeline: brainstorming → adversarial-design-review (3 cycles) → writing-plans → adversarial-plan-review → alignment-check → scope-lock → subagent-driven-development. 15 PRs across 15 plugin repos (3-implementer parallel team).
Remaining followups tracked separately: