Skip to content

fix(manifest): correct council worker.md sha256 after #22 - #28

Merged
jorisjonkers-dev-agents[bot] merged 1 commit into
mainfrom
fix/manifest-worker-sha
Jul 13, 2026
Merged

fix(manifest): correct council worker.md sha256 after #22#28
jorisjonkers-dev-agents[bot] merged 1 commit into
mainfrom
fix/manifest-worker-sha

Conversation

@jorisjonkers-dev-agents

Copy link
Copy Markdown
Contributor

PR #22 changed council/prompts/worker.md but did not refresh its manifest.yaml sha256, so validate_manifest fails on main and blocks CI on every agent-kit PR. This repins the digest to the committed files actual sha256 (verified: validate_manifest passes). No content change.

PRs #22 (council worker.md) and an earlier install.sh render left their
manifest.yaml sha256 pins stale, so validate_manifest — and therefore CI
on every agent-kit PR — fails on main. Repins both to the committed
files' actual sha256. render --check still passes (no content change);
validate_manifest now passes.
@jorisjonkers-dev-agents
jorisjonkers-dev-agents Bot force-pushed the fix/manifest-worker-sha branch from cb724d6 to 39a493c Compare July 13, 2026 10:13
@jorisjonkers-dev-agents
jorisjonkers-dev-agents Bot merged commit 8fade6a into main Jul 13, 2026
7 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