Skip to content

fix(release): add ManifestProvider so verify-capabilities gets plugin Name#24

Merged
intel352 merged 1 commit into
mainfrom
fix/release-pipeline-v0.2.10-manifest
May 24, 2026
Merged

fix(release): add ManifestProvider so verify-capabilities gets plugin Name#24
intel352 merged 1 commit into
mainfrom
fix/release-pipeline-v0.2.10-manifest

Conversation

@intel352
Copy link
Copy Markdown
Contributor

Root cause

The IaC bridge's GetManifest returns Name="" when no ManifestProvider is set. wfctl plugin verify-capabilities fails with name: plugin.json="workflow-plugin-hover"; binary Manifest.Name="" mismatch. Also: committed plugin.json.version was "0.2.0" not sentinel "0.0.0", causing version drift failure.

Fix

  • Embed plugin.json via go:embed in cmd/workflow-plugin-hover/main.go
  • Pass sdk.MustEmbedManifest as ManifestProvider in IaCServeOptions
  • Add goreleaser hook to copy plugin.json to cmd/ before build
  • Set plugin.json.version to sentinel "0.0.0"

… Name

The IaC bridge's GetManifest returns Name="" when no ManifestProvider is
set, causing wfctl verify-capabilities to fail. Fix:
- embed plugin.json via go:embed in cmd/main.go
- pass sdk.MustEmbedManifest as ManifestProvider in IaCServeOptions
- add goreleaser hook to cp plugin.json into cmd/ before build
- set plugin.json.version to sentinel "0.0.0" (goreleaser writes release version to archive)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@intel352 intel352 merged commit 3f2af3d into main May 24, 2026
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