Knit 0.1.0-alpha.31

Knit 0.1.0-alpha.31 improves history synchronization with resumable uploads, scoped cursor handling, and consistent handling of rewritten commits. Bundle-scoped uploads preserve project-wide cursor state so subsequent project synchronization can deliver pending history.

Release binaries are available for macOS, Linux, and Windows. Verify downloads using their accompanying SHA-256 checksum files.

v0.1.0-alpha.30

Fix

Fix HTTP 409 after successful local landing: ordinary bundle synchronization now waits for the complete run receipt instead of publishing it during finalization. Ownership-bound completion publishes the final receipt before releasing ownership; later sync reuses it unchanged.

Receipt-upload retries preserve completed steps. Existing saved landing plans remain usable without regeneration.

Knit 0.1.0-alpha.29

Changes

• Reuse saved attached-branch landing plans after new feature commits. Fresh apply fetches the current feature branch heads, merges and pushes, then runs configured commands in their saved order.
• Keep the plan unchanged and record actual sources per run. Resume continues those recorded sources.
• Preserve repository, branch, recipe and scope validation, and existing isolated/pinned workflows.
• Correct Windows line-ending assertions in branch-checkout tests.

Upgrade local and hosted Knit executors to use this behavior with existing branch-mode plans.

Knit 0.1.0-alpha.28

Changes

• Add project-configured attached branch checkouts for landing: update the target branch, merge and push, then run the recipe in the registered source checkout.
• Keep feature worktrees unchanged and record the current branch revision for commands, including resume.
• Use normal Git branch merge messages when integrating reviewed source commits.
• Gate the new checkout contract behind executor 0.5 and the branch-checkout capability; existing plans keep their original semantics.

New branch-checkout plans require updated local and hosted executors. Regenerate and review a plan after selecting checkout.mode: "branch".

Knit 0.1.0-alpha.27

Landing command output is now visible while commands run.

• Stream stdout and stderr from arbitrary configured commands, including noninteractive commands.
• Show Git fetch, merge, push, and checkout progress during landing and retain command receipts.
• Preserve interactive terminal access and machine-readable JSON results.
• Redact Git credentials across output chunks.

Includes regression tests for output arriving before command completion, recorded output, and repository merge/push execution.

Knit 0.1.0-alpha.26

This release adds support for current hosted project recipes and executable landing plans.

• Clone projects whose landing failure policy is stop or recover.
• Generate, validate, and execute schema 0.2 landing plans locally, including ordered repository workflows and mergeability preflight.
• Keep intermediate lane landings separate from terminal review merges, and synchronize landing plans and run history.
• Improve landing destination selection and distinguish base history from proposed bundle work.

Update with Homebrew:

brew update
brew upgrade knit-cli/tap/knit
knit --version

Expected version: knit 0.1.0-alpha.26.

Knit 0.1.0-alpha.25

Hosted bundle links now appear immediately below the ## Knit Bundle heading in PR descriptions.

Run knit publish sync to correct existing descriptions. Surrounding author text is preserved, repeated syncs do not duplicate links, and Bitbucket’s managed markers remain invisible.

Knit 0.1.0-alpha.24

Knit 0.1.0-alpha.24

This release polishes cross-repo review descriptions and records more
information about published pull requests.

• On Bitbucket, the start and end markers of Knit's managed bundle section in
  a review description are now invisible Markdown reference markers, so
  the managed section no longer shows stray delimiter text. knit publish sync repairs existing Bitbucket descriptions written by earlier versions,
  rewriting the managed section in place while preserving the surrounding
  user text (#209).
• Review descriptions now include a generic "View bundle" link at the top,
  shown when the sync service supplies a canonical URL for the bundle.
• knit publish create now pushes the feature branches and syncs the bundle
  to the configured sync service before creating review objects, then syncs
  the recorded review metadata afterwards, so the links in a new review
  description resolve from the start.
• Knit records, for each published review object, the host account that
  opened it as the host reports it (GitHub, GitLab, Forgejo, Bitbucket),
  including display name, avatar URL, and profile link when available. This
  author can differ from the person who made the bundle, for example when a
  bundle adopts a PR someone else opened. A refresh that gets no author from
  the host keeps the one already recorded.

Upgrading: no configuration changes are required; existing bundles and
review objects keep working. An existing bundle gains its "View bundle"
link once the URL is learned through a sync or push, or from the current
artifact recorded on the sync service. To refresh managed review
descriptions, run knit publish sync.

Ubuntu installations using the signed Knit APT repository can upgrade with:

sudo apt update
sudo apt install --only-upgrade knit
knit --version

Homebrew installations can upgrade with brew update && brew upgrade knit-cli/tap/knit. Platform archives, checksums, Linux packages, and
Homebrew bottles are attached to this release.

Knit 0.1.0-alpha.23

This release fixes token entry that could appear to hang when --token-stdin was used at a terminal.

• Run knit auth for guided setup of Git hosting credentials or a sync-service token.
• Run knit auth remote hosted --url https://host.example to configure a sync service directly. Paste the token at the hidden prompt and press Enter. Knit verifies it before saving.
• Run knit auth remote hosted to replace an existing sync token. Rejected tokens can be retried; cancellation and failed verification preserve the previous configuration. Use --offline only when deliberately saving without verification.
• Terminal use of remote add --token-stdin, remote token --token-stdin, and auth add --token-stdin now provides a hidden prompt that submits on Enter. Pipes remain supported for automation.
• Setup prints the actual token storage path and reports active environment overrides. An unavailable optional forge-capability check no longer fails a valid sync login.

Ubuntu installations using the signed Knit APT repository can upgrade with:

sudo apt update
sudo apt install --only-upgrade knit
knit --version
knit auth

Homebrew installations can upgrade with brew update && brew upgrade knit-cli/tap/knit. Platform archives, checksums, Linux packages, and Homebrew bottles are attached to this release.

Validation: 715 Linux CI tests passed, along with macOS and Windows CI. Signed APT upgrades from alpha.22 to alpha.23 were verified on Ubuntu 22.04 and 24.04; the installed binaries passed real-terminal token-entry, retry, cancellation, permissions, oversized-response, and timeout checks as an unprivileged user. Package-install CI also passed for amd64 and arm64 on both Ubuntu versions.

Homebrew was updated through homebrew-tap #11, with bottle-install CI passing on macOS and Linux. The automatic tap-update step reports a missing HOMEBREW_TAP_TOKEN; the manual publication is complete.

Knit 0.1.0-alpha.22

Fixes a severe slowdown in knit related on projects with large histories.

• Refresh the complete project history in one batch instead of rereading the ledger for every bundle.
• Batch commit-subject lookups when printing related history.
• Preserve archived and landed bundles, missing local events, recorded-only history, and cross-repository context.

A large-workspace comparison improved from 149.7 seconds to 0.66 seconds with all 3,280 output lines unchanged. Includes regression coverage for archived history recovery and idempotent refresh.

This release also includes the changes landed since alpha.21, including indexed history queries, Boolean query expressions, runtime dependency validation, and binary Homebrew distribution.

Pre-release binaries are provided for macOS (Intel and Apple Silicon), Linux (x86_64 and ARM64), and Windows (x86_64). Homebrew bottles are generated and verified by the release workflow.