Skip to content

Bump minEngineVersion 0.72.0 → 0.74.0 (apply→create needs ResourceDriver) — cut v1.2.1 #31

@intel352

Description

@intel352

Problem

plugin.json for v1.2.0 declares minEngineVersion: 0.72.0. The SPA loads and plans on engine v0.72.0, but the headline apply → CREATE resources → commit-back flow only works on workflow v0.74.0+, which wires providerclient.ResourceDriver end-to-end (workflow#851). On v0.72.0/v0.73.0 the apply step plans + hash-guards but never creates against an external provider (the adapter returns ErrProviderMethodUnimplemented).

So a user who wfctl installs workflow-plugin-infra v1.2.0 onto an engine v0.72.0 host gets a silently-degraded experience (plan works, apply creates nothing).

Fix

  • Bump plugin.json minEngineVersion0.74.0.
  • Cut workflow-plugin-infra v1.2.1.
  • Re-register in workflow-registry (refresh the manifest's minEngineVersion + the v1.2.1 assets/sha256).

Context

Discovered during the infra-admin Phase 2/3 cascade (scope amendment ADR 0021). The registry PR (#217) registered v1.2.0 with minEngineVersion: 0.72.0 mirroring the plugin's own plugin.json (registry-derives-from-source hygiene) rather than hand-editing the registry to a value the plugin source doesn't declare. This followup fixes it at the source.

Proven working combo: workflow v0.74.0 + plugin v1.2.0, scenario 92 (workflow-scenarios#74), 42/0/1.

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions