Skip to content

[Tracker]: v0.8.0 release queue and Stable-tier blockers #7112

@Audacity88

Description

@Audacity88

Summary

Tracker for the v0.8.0 release line: config and tool-call-parser Stable-tier promotion, schema/config breaking-change cleanup, runtime/provider configuration correctness, and release-default decisions that must be settled before v0.8.0.

This issue is the milestone coordination home. It is not approval for every linked PR, and it should not replace the Project board. Each linked PR still needs its own review, labels, validation, docs, and merge-readiness checks.

Problem statement

The v0.8.0 milestone has a clear description and a large set of scoped issues, but it does not currently have a standalone release tracker. That makes it harder to answer the practical maintainer questions:

  • Which items are true v0.8.0 blockers?
  • Which PRs are reviewable, blocked, or waiting for author action?
  • Which release-default or breaking-change decisions need docs/changelog follow-through?
  • Which adjacent tracks have their own tracker and should not be folded into this one?

Governance also expects the next active release to have a visible milestone tracking issue. This issue fills that gap for v0.8.0.

Blockers (26; must close or defer before v0.8.0 stable)

These are the true release blockers, re-vetted 2026-06-11 against the bar "broken behavior that can confuse users": every remaining open priority:p1/priority:p0 defect plus the release gate. Demoted in that pass: #5849 (Dream Mode — feature, not a defect) and #6127 (internal gateway hardening follow-up to #6099; its PR #7419 is already milestoned v0.8.1) — both moved to v0.8.1 at p2. The parenthetical shows open-PR coverage from a live GitHub search; "no open PR" means no open PR reference was found and the item needs an owner or an explicit deferral. These items live only here, not in the full queue below.

Three blockers (#7042, #7462, and #7470) currently have no open PR reference; all other open blockers have at least one open PR.

Proposed use

  • Track v0.8.0 release scope in one public issue.
  • Keep config/schema/tool-call-parser Stable-tier work visible.
  • Keep runtime/provider configuration correctness work visible when it affects v0.8.0 behavior.
  • Record release-default decisions that affect installs, feature bundles, docs, or upgrade expectations.
  • Keep adjacent tracks linked but separate. For example, the Zerocode/TUI track belongs in [Tracker]: Zerocode #6826, not here, unless a TUI item blocks the v0.8.0 release itself.
  • Do not treat this tracker as a blanket approval. Linked work still needs normal review, validation, and release-note hygiene.

Full queue (non-blockers)

Everything else tracked for v0.8.0: merged and closed history, p2 and unprioritized work, and the audit-added items. These are in scope for v0.8.0 but are not release blockers — the blocker line is the section above. Each item lives in exactly one place: blockers above, everything else here.

Current PR queue (170 total: 85 open, 85 closed)

Active v0.8.0 PRs (74 total: 8 open, 66 closed)

Current issue queue (51 total: 27 open, 24 closed)

Config, schema, provider routing, and Stable-tier promotion (5 total: 1 open, 4 closed)

MCP, tool filtering, and tool-call parser behavior (2 closed)

Open MCP/tool-filter blocker work is now in the Blockers section: #6699, #6721, #6873, and #6874. PR #6861 remains in the open PR queue as the active #6699 implementation path. Below is the landed history.

Multi-agent, channel, memory, and gateway behavior (4 total: 2 open, 2 closed)

Plugin/security items moved out of v0.8.0 (1 closed)

Plugin SSRF and zc_env_read allowlist work moved to the v0.8.2 WASM/plugin program tracker (#7314).

Untracked v0.8.0 PRs (82 total: 63 open, 19 closed; added 2026-06-09 audit, refreshed 2026-06-11)

Added 2026-06-11 audit (new open PRs in the v0.8.0 milestone)

Untracked v0.8.0 issues (30 total: 24 open, 6 closed; refreshed 2026-06-11 audit)

Adjacent trackers (linked but separate, not v0.8.0 line-items): #6823 (TUI ACP Bridge) and #6825 (TUI UX) belong to the Zerocode/TUI track under #6826 per this tracker's scope rule, and are listed here only for visibility. They are not v0.8.0 release blockers unless a specific TUI item blocks the release itself.

Recent closures not previously listed (9 closed)

Acceptance criteria

  • Every v0.8.0 PR is either merged, explicitly deferred, superseded, or still listed with a clear next action.
  • Config/schema/tool-call-parser Stable-tier blockers are closed or explicitly deferred before release.
  • Breaking or default-behavior changes include docs and changelog coverage.
  • Release/install feature-bundle decisions are explicit, especially where source builds, packaged builds, and docs could imply different defaults.
  • Adjacent work with its own tracker, such as Zerocode/TUI in [Tracker]: Zerocode #6826, stays linked but does not blur this release queue.

Architecture impact

This tracker does not make code changes. It coordinates work that may touch zeroclaw-config, zeroclaw-tool-call-parser, zeroclaw-runtime, zeroclaw-providers, zeroclaw-channels, zeroclaw-gateway, zeroclaw-tools, plugin host functions, release docs, and install/default feature guidance.

Risk and rollback

This is a tracker. Risk lives in the linked issues and PRs. If this grouping becomes stale, update the checklists, move items to a better tracker, or close this issue after the release queue is resolved.

Breaking change?

No. This issue tracks potentially breaking v0.8.0 work, but it does not itself change behavior.

Data hygiene checks

  • I removed personal/sensitive data from examples, payloads, and logs.
  • I used neutral, project-focused wording and placeholders.

Metadata

Metadata

Assignees

No one assigned

    Labels

    configAuto scope: src/config/** changed.enhancementNew feature or requestpriority:p1High priorityrisk: highAuto risk: security/runtime/gateway/tools/workflows.runtimeAuto scope: src/runtime/** changed.securityAuto scope: src/security/** changed.status:acceptedRFC or work item accepted and ratified by the team.toolAuto scope: src/tools/** changed.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    Backlog

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions