Release v3.36.0 - #223
Merged
Merged
Conversation
…rs (#222) Don't auto-feed outsider issue bodies into the agent. --self is @me-only and too narrow for a machine user claiming the owner's issues; --collaborators uses the live host-API collaborator list (fail closed) and --trusted-authors unions extra friend logins into that pool only while the collaborators gate is on.
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
1 participant
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.
Release v3.36.0
Released: 2026-09-02
Highlights
/do:next --issuescan claim a collaborator's work, not just your own.--selfstays@me-only;--collaboratorsuses the live GitHub/GitLab collaborator list (fail closed) so a machine user can pick up the owner's issues without ingesting outsider issue bodies.--trusted-authorsunions extra logins into that pool only while the collaborators gate is on — it is not a saved collaborator allowlist, and it does nothing when the gate is off.--swarmand explicit#<num>. Auto-pick skips outsider authors, an explicit number for someone outside the pool is refused (not overridden), and swarm workers inherit the orchestrator's resolved--collaborators/--trusted-authorsso a saved default cannot widen the batch.Added
/do:next --collaborators/--no-collaborators: security gate that restricts issue claims to authors in the live host-API collaborator set. GitHub usesrepos/:owner/:repo/collaborators; GitLab uses project members withaccess_level >= 30(Developer). Fetch failures and an empty login set abort rather than falling open to any-author or to--trusted-authorsalone./do:next --trusted-authors <list>: extra GitHub/GitLab logins unioned into the collaborators gate. Validated login shape, case-insensitive compare,none/empty tombstone. No effect when--collaboratorsis off./do:config --collaborators/--trusted-authorssaved defaults (global or--project), with--unsetsupport. Only/do:nextreads these keys.Changed
--selfremains the stricter@megate and wins when both are on.--no-selfdoes not disable collaborators mode.--collaborators/--no-collaboratorsand--trusted-authors <list>/noneso they do not re-resolve a different saved default./do:config, andlib/review-config-defaults.mddocument the new flags, defaults, and fail-closed collaborator fetch.Full Changelog
Full Diff: v3.35.3...v3.36.0