Repository navigation
fix(context-cli): valid workflow revision before requirements exist; release 0.7.100 - #112
Merged
Merged
Conversation
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Before production requirements exist (
src/indexers.yamlmissing), the production-planning Route used the placeholder revisionrequirements-configuration. Its required resourcecontext.source-boundaryis delivered ascontext resource materialize … --revision <revision>, which only acceptssha256: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
context status, checks its revision is asha256:value and runs every printedresource materializecommand (normal and managed). It failed on main with the placeholder and passes now.🤖 Generated with Claude Code