Skip to content

fix(context-cli): valid workflow revision before requirements exist; release 0.7.100 - #112

Merged
qiansc merged 2 commits into
mainfrom
fix/requirements-route-revision
Nov 16, 2026
Merged

qiansc merged 2 commits into
mainfrom
fix/requirements-route-revision

Conversation

@qiansc

@qiansc qiansc commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Summary

Before production requirements exist (src/indexers.yaml missing), the production-planning Route used the placeholder revision requirements-configuration. Its required resource context.source-boundary is delivered as context resource materialize … --revision <revision>, which only accepts sha256: workflow revisions, so the command the CLI printed always failed with "workflow revision is invalid". The Route now uses the graph evaluation's revision, which the status output reports as the workflow revision too, so the printed command runs and the staleness check is kept.

Release 0.7.100 (same version file set as 0.7.99).

Tests

  • The bootstrap test now reads the Route printed by context status, checks its revision is a sha256: value and runs every printed resource materialize command (normal and managed). It failed on main with the placeholder and passes now.
  • 81 related test files: 449 pass; typecheck and lint clean.

🤖 Generated with Claude Code

qiansc and others added 2 commits November 16, 2026 13:01
…orkflow revision

Before src/indexers.yaml exists the production-planning Route used the
placeholder revision requirements-configuration, which resource materialize
rejects, so its printed context.source-boundary command always failed. Use the
graph evaluation's revision.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@qiansc
qiansc merged commit bd5251f into main Nov 16, 2026
2 checks passed
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