v0.4.0

Features

• Add init, doctor, and bootstrap commands alongside .patchlane.yml config support, letting you scaffold, validate, and run Patchlane without repeating CLI flags. Agent skills now default to the installed package version instead of main.

Improvements

• Reject patch branches that contain upstream commits not present in the selected source, preventing unsafe rebases. Add the --source option as a cleaner way to specify upstream releases or branches.

v0.3.1

Features

• Added --force-push flag to push the sync branch even when it appears unchanged.

Improvements

• Dry-run now applies patches in a temporary worktree to accurately detect conflicts without modifying local state.

v0.3.0

Features

• Patch changes are now replayed as individual commits with preserved metadata, and patches that depend on generated sync output are rejected by default (use --allow-dependent-patches to override).

Improvements

• --dry-run now validates patches without creating a local branch; use --no-push to build the sync branch locally without pushing.
• Sync output now includes rich patch diagnostics showing commit counts, changed files, and ancestry warnings.

v0.2.4

Add agent skills

Adds agent skills for patchlane workflows.

v0.2.3

What's New

Fixes a bug with dry-run
Dry-run is now a proper boolean flag.

v0.2.2

What's New

Fixes a bug with divergent branches

When a patch branch is based on an upstream release that is not an
ancestor of the target upstreamBase (e.g., v1.14.25 patch applied on
v1.14.28), the three-dot diff upstreamBase...resolved includes
intermediate upstream changes from the merge-base, causing spurious
conflicts.

This fix detects when upstreamBase is not an ancestor of the patch
branch, finds the oldest unique commit in the patch history, and uses
a smarter diff base:

• If that commit is tagged (likely a release the patch was based on),
  use the tagged commit itself as the diff base.
• Otherwise, use the parent of the oldest unique commit.

This ensures only the actual patch changes are applied, excluding
upstream release changes that may conflict with the target base.

v0.2.1

What's New

Avoids republishing duplicate branches
Patchlane now uses tree hashes to avoid republishing if the content is identical.

v0.2.0

What's New

CLI-First Architecture
Patchlane is now a pure npm CLI tool. The reusable GitHub Actions workflows have been removed entirely. Consumers run npx patchlane directly inside their own workflow steps.

Auto-Configured Git Identity
Patchlane now sets a default git identity (github-actions[bot]) automatically when user.name or user.email is missing. Consumers no longer need a separate "Configure git identity" step in their workflows.

Updated Documentation

• README and examples now reflect the CLI-only usage model
• Package description updated to match

v0.1.0

Initial release of patchlane as an npm package.

What's new:

• Published to npm — install with npx patchlane
• New CLI commands: patchlane sync and patchlane promote
• Reusable GitHub Actions workflows now use npx patchlane@latest internally
• Automated npm publishing on release creation