Update agent-loop to 0.16.6 and keep replay provenance in sync - abandoned - #114
Open
renovate[bot] wants to merge 5 commits into
Open
Update agent-loop to 0.16.6 and keep replay provenance in sync - abandoned#114renovate[bot] wants to merge 5 commits into
renovate[bot] wants to merge 5 commits into
Conversation
|
Tick the box to add this pull request to the merge queue (same as
|
renovate
Bot
force-pushed
the
renovate/voku-agent-loop-0.x
branch
from
August 17, 2026 06:05
7eab8fb to
98484d2
Compare
renovate
Bot
force-pushed
the
renovate/voku-agent-loop-0.x
branch
from
August 17, 2026 06:08
98484d2 to
f357d26
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
|
Contributor
Author
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
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.



What changed
voku/agent-loop 0.16.5to0.16.6agent_loop_releaseprovenance to the same releasetoolchain.agent_loop_releasein dogfoodissue-*.jsonfiles as the same Packagist dependencyvoku/agent-loopWhy
The dogfood verifier intentionally requires the replay input and the repository-local Composer tool project to agree on the direct
agent-looprelease. A normal Renovate Composer bump therefore left the PR deterministically red until the replay provenance was changed by hand.The repository also now treats
agent-loopas the single root authority for its siblingagent-*release set, so transitive packages such asagent-sessionmust not be pinned independently here. Their resolved versions remain evidence, not another dependency authority.This keeps the fail-closed replay contract while making the valid dependency update atomic in future Renovate PRs.
Validation
verify-release-set.phpremains unchanged and continues to enforce the ownership boundary