Skip to content

fix(workflow-compat): allow_no_entry_points on module-only testdata - #16

Merged
intel352 merged 2 commits into
mainfrom
fix/workflow-compat-allow-no-entry-points
May 21, 2026
Merged

intel352 merged 2 commits into
mainfrom
fix/workflow-compat-allow-no-entry-points

Conversation

@intel352

Copy link
Copy Markdown
Contributor

Recent wfctl tightening (config must have entry points) started rejecting the module-only testdata/compat-strict-proto-config.yaml fixture, breaking workflow-compat CI on every PR. Fix: add allow_no_entry_points: true per the engine's documented escape hatch for embeddable / module-only validation fixtures.

intel352 and others added 2 commits May 21, 2026 15:43
The workflow-compat job runs `wfctl validate` against this testdata to
verify backward-compat for `step.audit.poll_anchor_confirmation` and
`step.audit.public_receipt` under STRICT_PROTO. The config is module-only
(audit.ledger + audit.anchor_provider.opentimestamps) with no entry
points — a recent wfctl tightening (config-must-have-entry-points)
started rejecting these embeddable-style configs.

Add `allow_no_entry_points: true` per the engine's documented escape
hatch for embeddable sub-workflows / module-only validation fixtures.

Unblocks workflow-compat CI on PRs touching this repo.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…(not YAML field)

Prior commit added `allow_no_entry_points: true` to the testdata YAML, but
that key isn't a config field — wfctl parses it as CLI flag
`--allow-no-entry-points`. Revert the YAML change; add the flag to the
wfctl validate invocation in .github/workflows/workflow-compat.yml instead.

Engine reference: `cmd/wfctl/validate.go:22` defines
  fs.Bool("allow-no-entry-points", false, "Allow configs with no entry
  points (triggers, routes, subscriptions, jobs)")

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@intel352
intel352 merged commit 313e55e into main May 21, 2026
7 checks passed
@intel352
intel352 deleted the fix/workflow-compat-allow-no-entry-points branch May 21, 2026 20:03
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