Skip to content

Release v0.6.6 - #25

Merged
d3cker merged 30 commits into
mainfrom
release
Sep 19, 2026
Merged

d3cker merged 30 commits into
mainfrom
release

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Publish v0.6.6 to main with all released changes and the updated package download.

Release: https://github.com/d3cker/opencode2-github-automation/releases/tag/v0.6.6

Documentation

  • Align all eight bot workflow diagrams and runtime/recovery references with the
    implementation, including owner lifecycle, feedback queuing, session recovery,
    verification gates, merge polling and TUI commands.
  • Require documentation and affected diagrams to be updated with each relevant
    implementation change in repository and bundled bot instructions.

Fixed

  • Restore compatibility with OpenCode 2.0.6: update the pinned SDKs, discover
    services through /api/info, refresh owner activity with session.update,
    and interrupt sessions with resume: false. Replace the removed headless
    activation command with location-scoped plugin.list and document validation.

  • Honor formal approvals for the exact verified PR commit even when publication
    or description recovery finishes later. Retain review revocation, authorization,
    and merge-readiness checks; keep timestamp gating for unbound merge comments.

  • Retry PR head propagation after a successful push when the remote branch still
    matches the verified commit. Preserve a durable push checkpoint across restarts,
    avoid repeating acknowledged pushes, and distinguish closed PRs from changed
    branches while preserving manual description edits.

  • Keep repository inventory RPC responses valid JSON when an owner has no runtime
    snapshots. Isolate setup-test registries so validation never adds fixture
    repositories to the operator's inventory.

  • Use the successful session's final completion report as the PR description instead
    of its initial acknowledgement. Persist reports across restarts, retain the
    original summary plus the latest follow-up, distinguish dispatcher checks from
    agent-reported tests, and preserve manual notes outside the managed section.

  • Reconcile timed-out or interrupted sessions completed manually after a blocked
    task or service restart. Verify and publish through the dispatcher, then process
    queued issue feedback on the same branch and PR, including legacy checkpoints.

Added

  • Per-repository autoApproveRepositoryFiles configuration, an opt-in setup
    prompt, and init --auto-approve-repository-files. Bot sessions and native
    workers can automatically access files in the repository and assigned worktree
    across rounds/restarts, without global permission changes. Explicit denials,
    pending questions, media-helper limits, and shell permissions remain unchanged.

  • Cancel a single bot round while retaining issue/PR tracking, with durable stop
    recovery, preserved draft worktrees and fresh worktrees for later feedback.
    Resume tracking a locally closed task without replaying its abandoned round
    or old comments. Expose both actions in /bot and the CLI; show historical
    errors only in details after closing or cancelling.

  • List configured repositories across the host with opencode2-automation list
    (--json for scripts) and /bot → Repositories. Show owner/checkout paths,
    base branches, timestamped dispatcher/scheduler status and concrete issue
    failures without activating other bots. Register projects during init/startup;
    import older inactive standard configurations with list --discover <root>.
    Preserve missing entries and explicitly mark stopped, stale or unavailable data.

  • Manage tasks directly from /bot: inspect details, open sessions, close idle
    tabs, restart workflows, or stop sessions and durably end tracking without
    deleting work. Preserve closed tasks as history and skip rediscovery, feedback,
    runtime hooks and publication after closure, including missing issue/PR cases.

  • Identify blocked, failed and closing issue keys and errors in the runtime
    sidebar instead of showing only an anonymous attention counter.

  • Add a live BOT RUNTIME sidebar and /botstatus report with dispatcher operations,
    scheduler scans/retries, queue counts and selected-task details. Keep stale and
    unavailable readings explicit; monitor through read-only owner-scoped RPC.

  • Validate native sidebar rendering, reactive updates and narrow layouts as part
    of the standard check command using pinned TUI/Bun development dependencies.

  • /restartworkflow and the matching CLI/RPC command resume a stopped task from
    its saved stage, preserving worktrees, sessions, PRs, and feedback. Checkpoint
    continuation requests across restarts without bypassing checks or permissions.

Changed

  • Collect feature PRs on devel without publishing a release. Run CI on PRs to
    devel and release, and publish automatic patches only after a same-repository
    devel to release PR is merged.
  • After stable publication and README update, automatically merge the published
    release head into devel without a synchronization PR. Preserve new development
    commits, retry concurrent updates, and fail safely on conflicts or denied pushes.

Merge this PR with a merge commit to preserve the long-lived release branch.

d3cker and others added 30 commits September 15, 2026 13:55
# Conflicts:
#	docs/releases.md
Fix stalled workflows and integrate development on devel
feat: show live bot runtime status in TUI sidebar
Manage and close bot tasks from /bot without losing work
Add host repository inventory to CLI and /bot
Publish final session summaries in PR descriptions
Cancel individual bot rounds while keeping issue tracking
Fix repository inventory RPC for inactive owners
Retry PR publication while GitHub catches up with the pushed commit
Preserve approval of the same commit across publication recovery
Restore compatibility with OpenCode 2.0.6
Add per-repository automatic file approvals
Release v0.6.6 from devel
@d3cker
d3cker merged commit bf1c9db into main Sep 19, 2026
1 check 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