Skip to content

GitDocket v0.4.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 17 Sep 22:45
· 26 commits to main since this release
v0.4.1
a9991ff

GitDocket 0.4.1

GitDocket 0.4.1 installs both commands with one Homebrew command and adds reusable project workflows. It preserves the published 0.3.1 and partially published 0.4.0 workflow merge bases.

Teams can inspect and install versioned local Markdown packages, configure project choices, discover qualified workflows, update packages independently of GitDocket, and disable or remove them while retaining project records. Conservative reconciliation exposes local edits, incompatible content and interrupted operations. Mechanical validation reports its limits without executing package code.

The extension guide and Beacon example demonstrate a product-delivery process from reviewed request to verified local handoff, with reusable decisions for later work. A second incident-review package demonstrates independent authoring and composition. Optional recipes use tools already exposed by the agent host, including MCP; the host owns connections and credentials. Custom UI/statuses, executable plugins and background synchronization remain outside this version.

Qualification includes actual Codex sessions, real browser downloads, local synthetic MCP success/failure/uncertainty, fresh-session recovery, historical/customized upgrades, and macOS/Linux package checks. Claude adapters are generated, but Claude behavior remains unqualified in the tested environment because authentication was unavailable. Synthetic review and provider fixtures are not human approval or live delivery.

This candidate also fixes Git updates in linked worktrees on Linux when a missing private refs directory deferred its filesystem error until iteration. Direct watcher and Serve regressions verify shared refs, detached HEAD changes and packed refs without increasing timeouts.

Installation

brew install gitdocket/tap/gitdocket
docket --version
docket-mcp --version

The project-maintained formula installs standalone CLI/MCP executables, embedded browser resources and retained upgrade history. No separate Bun, Node or npm installation is needed. Release qualification combines Ubuntu 24.04 ARM64/x64 checks in Linux-only GitHub Actions with local Mac ARM64 and Rosetta-assisted Intel checks; receipts record the actual Mac OS and assistance. The formula supports macOS 15+ and Homebrew-compatible glibc Linux on those architectures. Windows is not supported.

Node 22+ users can instead run npm install -g --include=optional @gitdocket/cli@0.4.1 @gitdocket/mcp@0.4.1. The existing npm names now launch exact-version platform packages containing the same binaries as Homebrew. The core/web libraries remain Bun-based. Source development and the Beacon example app still require Bun.

Use your package manager to update the executables. In each project, review docket upgrade --dry-run --json before applying docket upgrade and resolving any reported conflicts or retained differences. Package installation, updating and removal preserve project bundles; they do not reconcile project instructions automatically. If switching from npm/Bun, inspect command precedence and custom MCP paths using the migration guide.

Qualification exercises both installation routes, npm/npx, browser resources, actual MCP tooling, historical/customized/stale project upgrades, Homebrew reinstall/revision upgrade/uninstall, and failed checksum/download recovery. Release artifacts include source identity, licenses, checksums and native verification receipts. All eight coordinated npm packages use 0.4.1.

Markdown authoring guidance now preserves unwrapped paragraphs and simple list items, and lint reports accidental hard wrapping. Existing project content is never silently reformatted.

Publication recovery

This patch release completes the installation launch after 0.4.0 publication stopped during npm registry propagation. The publisher now waits up to ten minutes for version, provenance and tag visibility, bounds each metadata lookup and records accepted writes and verification progress immediately. Regression checks cover delayed visibility, safe resumption and immutable conflicts. The existing 0.4.0 tag and published packages remain unchanged.

Verification

Assets 15
Loading