Skip to content

GitDocket v0.3.1

Choose a tag to compare

@github-actions github-actions released this 13 Sep 03:23
· 29 commits to main since this release

GitDocket 0.3.1

GitDocket 0.3.1 makes retained workflow differences explicit during upgrades and gives the website’s documentation headings more breathing room.

Upgrade review

docket upgrade now labels retained workflow differences review in human output and returns a reviewRequired path list in JSON, with reviewRequired: true on affected items. This includes clean merges and unchanged files whose origin already matches the current version. A current stamp or conflict-free merge does not prove that current instructions arrived: compare retained differences with the shipped workflow and preserve confirmed project requirements.

The JSON action continues to describe the file operation. Review items preserve project-owned text and do not change the exit status; merge conflicts still return a nonzero status.

Historical upgrade checks now run in the normal test suite and against installed candidate packages during release qualification. They cover clean historical workflows, deliberate customization, stale version stamps, incomplete conflict resolution, repeat upgrades and preservation of authored guidance. Published 0.3.0 workflow bodies remain frozen as merge bases.

Website spacing

Documentation section headings now have consistent space above them: 48px on desktop and 40px on mobile, with smaller subheading gaps. The shared stylesheet handles both wrapped sections and headings directly in the page, avoiding cramped transitions or doubled spacing. All eight pages were checked at desktop and narrow mobile widths.

Upgrade

bun add --global @gitdocket/cli@0.3.1 @gitdocket/mcp@0.3.1

Restart Serve processes and reconnect MCP clients. In each existing project, run docket upgrade --dry-run, review the plan, then run docket upgrade. Reconcile conflicts and retained differences before treating the upgrade as complete, then run docket index and docket lint. This release does not automatically replace project-owned workflow differences.

All four packages (core, web, cli, and mcp) use version 0.3.1. No project-document migration is required.

Verification