Skip to content

chore(autoducks): update machinery to v0.5.7 - #1

Closed
autoducks[bot] wants to merge 1 commit into
mainfrom
autoducks/update-0.5.7
Closed

chore(autoducks): update machinery to v0.5.7#1
autoducks[bot] wants to merge 1 commit into
mainfrom
autoducks/update-0.5.7

Conversation

@autoducks

@autoducks autoducks Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Version

0.5.20.5.7 · channel: stable

From b062c9a0ab871d9ee5dbb0bce1a430b27dbc36ee to 6044f50035839e03c1a28f43d3de780929ffd3a4.

Changelog

Fixed

  • fix(agent): Read belongs in the tool floor too (#1176)

Fixed

  • fix(agent): a tool floor the definition cannot replace away (#1174)

Fixed

  • fix(feedback): a max_turns retry hint for the agent lane (#1172)

Fixed

  • fix(agent): honour surface: both, and stop double-posting refusals (#1170)

Security

  • The custom-agent lane now reads agent definitions — and the custom_agents
    config keys that grant them tools — from the base branch, never from the
    checked-out tree. On a pull request the checkout is refs/pull/N/head, and a
    definition body becomes the agent's prompt, so the previous behaviour could
    execute unreviewed content with the repository's token. This applies to both
    discovery and prompt assembly. (#1168)

Changed

  • Behaviour change for /agent: a definition that exists only on a pull
    request is no longer discovered, so an agent cannot be tried from the pull
    request that introduces it. Merge the definition to the default branch first,
    then use it. A /agent run on a pull request still works and still takes that
    pull request as its context; only the definition comes from elsewhere. (#1168)
  • Removed the machinery this replaces: the verified descriptor field, the tool
    clamp and its unverified_tools floor, the unverified-definition refusal, and
    the custom_agents.allow_unverified opt-in. None of these were part of a
    release, so no configuration needs migrating. (#1168)

Migrations applied

No migrations were required.

Verification

[1/6] bash-syntax: PASS
[2/6] json-yaml: PASS
[3/6] runtime-sync: PASS
[4/6] update-triggers-idempotence: PASS
[5/6] plugin-compilation-sync: PASS
[6/6] tree-integrity: PASS

verify-machinery: 6/6 checks passed

Rollback

Set update.pin to b062c9a0ab871d9ee5dbb0bce1a430b27dbc36ee in autoducks.json and re-run /update, or revert this PR.

@ggondim

ggondim commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Superseded by v0.5.8, released minutes ago. Closing so the updater opens a PR straight to the current version instead of landing an already-stale v0.5.7.

@ggondim ggondim closed this Aug 4, 2026
@ggondim
ggondim deleted the autoducks/update-0.5.7 branch August 4, 2026 00:05
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