Skip to content

Dev Command Center v0.1.30

Latest

Choose a tag to compare

@github-actions github-actions released this 25 Jul 23:31

v0.1.30 Release Notes

Highlights

  • Added fork-safe delivery workflows that preserve source repository identity
    while keeping pushes, reviews, and merge targets explicit.
  • Expanded the Inspector with normalized GitHub and GitLab review state,
    approval requirements, pipelines, jobs, and actionable failure context.
  • Added assisted recovery for Git and pipeline failures, plus a configurable
    Delivery Gate that derives whether work is blocked, needs attention, is ready,
    or has been delivered.
  • Brought live agent activity and delivery context into the workspace rail.

Fork-Safe Delivery

  • Workspaces now retain source and target repository metadata instead of
    assuming that every branch should be delivered through the default remote.
  • Push and change-request actions resolve the intended remote, repository,
    branch, provider, and authenticated forge account before making changes.
  • GitHub pull requests and GitLab merge requests share normalized review data
    while preserving provider-specific concepts and links.

Review, Pipelines, and Recovery

  • The Inspector now surfaces reviewers, pending approvals, review decisions,
    pipeline status, jobs, and failure details for GitHub and GitLab.
  • Delivery failures capture a structured snapshot and are classified into
    actionable categories such as authentication, permissions, branch conflicts,
    protected branches, and failing checks.
  • Recovery guidance offers safe retry or follow-up actions based on the current
    failure instead of leaving raw Git or provider errors without context.

Delivery Gate

  • Delivery Status combines local changes, commits, review state, approvals,
    conflicts, and pipeline health into a single derived state.
  • Repositories can define delivery policies for required approvals, clean
    pipelines, resolved discussions, and other merge-readiness expectations.
  • The workspace rail reuses this delivery context to show compact progress,
    elapsed activity time, recent completion state, and PR or MR readiness.
  • Rail metadata refreshes at a lower background cadence than the active
    Inspector to keep provider and Git activity predictable across many visible
    workspaces.

Models and Validation

  • Added Claude Opus 5 to the Claude Code model catalog and migrated legacy Opus
    aliases to the current model identifier.
  • Added an opt-in authenticated smoke harness for validating GitHub and GitLab
    delivery flows against real repositories without running in the default test
    suite.
  • Added regression coverage for review normalization, failure classification,
    recovery actions, delivery policies, workspace activity timestamps, rail
    recaps, and model resolution.

Validation Before Publishing

  • Run desktop type checks: yarn workspace @dcc/desktop typecheck
  • Run the complete desktop test suite: yarn workspace @dcc/desktop test
  • Build the desktop application: yarn workspace @dcc/desktop build
  • Run the Rust workspace tests: cargo test --workspace
  • Check the Tauri crate: cargo check --manifest-path src-tauri/Cargo.toml
  • Confirm release metadata is 0.1.30 in package.json,
    sidecar/package.json, sidecar/src/index.mjs, src-tauri/Cargo.toml, and
    src-tauri/tauri.conf.json.