Version Packages

[github-actions]

Summary

All bumped packages.

Package	From	To
hayate-cli	6.1.0	6.2.0
hayate	6.1.0	6.2.0

Changelogs

2026-07-25-resume-cli.md

Show Bumped Packages (3)

Package	Bump
npm:hayate	minor
cargo:hayate-cli	minor
cargo:hayate	minor

Resumable transfers, rate limiting, and a richer CLI

• Resume interrupted transfers: hayate receive --resume continues a partial
  single-file transfer from the last complete 4 MiB frame instead of restarting.
  An already-complete file is hash-verified without re-sending payload. (Wire
  protocol v7: the receiver now sends an 8-byte resume offset after accepting;
  v6 and v7 peers refuse to pair rather than mis-transfer.)
• Bandwidth cap: hayate send --bandwidth-limit 10MiB throttles sustained
  send throughput (also available as HayateSender::bandwidth_limit).
• Named peers: hayate peers add/list/remove saves receiver addresses;
  hayate send <path> --to NAME dials by name. Direct sends auto-remember the
  peer by IP.
• Interactive send: omit the path for a file prompt, or use --pick to scan
  the LAN and choose a receiver from a list.
• Transfer history: every completed transfer is logged locally;
  hayate history prints it (--clear to wipe, --format json for JSONL).
• Integrity report: receivers print an explicit "integrity verified" line
  and emit a matching JSON event after each transfer.
• receive --once: exit after the first completed transfer. Without it,
  direct-mode receive now keeps listening for more transfers.
• JSON schema tag: every --format json event now carries
  "schema": "hayate/1" for version-locked parsing.
• Man pages: release archives and .deb packages now ship a hayate(1)
  man page generated from the CLI definitions (man hayate).

Fixes

• Windows binary builds no longer fail with tar: Cannot connect to D: —
  GNU tar on Git for Windows treated the drive-letter colon as a remote host;
  the build script now passes --force-local.
• The publish workflow triggers release binaries via the GitHub REST API
  instead of the gh CLI.

Polish and hardening

• API stability: the semver-guaranteed surface is now explicitly runner
  • crate-root re-exports; transfer/tar/pool internals are
    #[doc(hidden)] and unstable. CI runs cargo-semver-checks.
• Version tolerance: v7 receivers gracefully accept v6 senders (resume is
  simply disabled); truly ancient/future versions fail fast with
  ProtocolMismatch instead of hanging.
• UI correctness: all progress bars/spinners are owned by a single
  TransferUi — no more leaked bars on error paths, and resumed transfers
  seed the bar at the resume offset so speed/ETA math is honest. Bar creation
  is gated uniformly by the output policy (JSON/plain/quiet never draw bars).
  The ESC/q listener now backs off while interactive prompts own the terminal.
• Refactor: send/receive share stage handling, consent/progress closures,
  success reporting, and a single PathCompleter; history recording is one
  record_transfer call instead of triplicated struct literals.
• Tests: 84 total — golden wire-format fixtures, protocol version gate
  (ancient + future), resume edge matrix (sub-frame partial, verify-only
  complete file), and assert_cmd-driven CLI integration tests (peers, history,
  docs, man, error paths) with isolated HOME.

Publish

The following packages will be published if merged:

Package	Version	Registry
hayate	6.2.0	cargo

[ShiinaSaku]

📚 DocuWriter Autopilot Preview

• Wire protocol structures, compatibility surfaces, and protocol benchmarking — Update wire protocol versioning and compatibility details to include protocol v7 and the new resume offset handshake. Apply suggestion 1
• Sender orchestration, transfer abstractions, and buffer management — Add bandwidth_limit to the documentation for HayateSender's public engine boundary. Apply suggestion 2
• Peer discovery library module and CLI integration — Update discovery/peer documentation to include named peers, peer persistence, and dialing by name. Apply suggestion 3

What's this? DocuWriter detected potential doc updates from this PR. Learn more