Repository navigation
Modernize plugin release metadata for publishable CMS releases #23
Description
Context
While removing the custom CMS /metrics endpoint in PR #22, I checked whether we could tag a plugin release after merge. The repo currently has no tags/releases, and publish validation fails independently of PR #22.
Current failure
$ GOWORK=off go run github.com/GoCodeAlone/workflow/cmd/wfctl@v0.64.3 plugin validate --file plugin.json --strict-contracts
FAIL workflow-plugin-cms v0.1.0-alpha (plugin.json)
- downloads: external plugins must have at least one download entry
- contracts: missing_module_contract_descriptor: module type "analytics.injection" has no strict contract descriptor
- contracts: missing_module_contract_descriptor: module type "cms.engine" has no strict contract descriptor
- contracts: missing_module_contract_descriptor: module type "cms.static_serve_before_dynamic" has no strict contract descriptor
- contracts: missing_module_contract_descriptor: module type "cms.tenant_resolver" has no strict contract descriptor
- contracts: missing_step_contract_descriptor: step type "step.cms_bundle_activate" has no strict contract descriptor
- contracts: missing_step_contract_descriptor: step type "step.cms_render_page" has no strict contract descriptorNeeded
- Add release download entries and current
.release/plugin.jsongeneration behavior. - Add/align strict contract descriptors for CMS modules and steps.
- Update the release workflow to use the current setup-wfctl pattern instead of the hardcoded v0.63.2 binary download.
- Tag the first publishable CMS release only after publish validation and runtime capability verification pass.
Activity
intel352 commentedon May 25, 2026
Fixed by PR #24 and release v0.1.0. The release now ships downloads, strict contract descriptors, embedded manifest metadata, and passes the publish/runtime release gates.