LFS Cloud v0.2.7

• [added]: Stream one flushed progress line for each target-missing migration upload, including its sequence, OID, and size.
• [added]: Add global --quiet error reporting that retains the previous concise failure output.
• [changed]: Stop prompting for the gcloud executable during interactive Google Drive setup while retaining explicit executable overrides.
• [changed]: Publish direct installer assets as install.sh and install.ps1 instead of the longer prefixed names.
• [changed]: Show parse causes or redacted expected and received URLs when migration rejects an upload action URL.
• [changed]: Show concrete cause values and automatically captured Rust backtraces for command failures by default.
• [changed]: Infer repository client server addresses from configured LFS Cloud URLs when --server is omitted.
• [changed]: Display migration object sizes and byte totals with human-readable decimal units.
• [removed]: Remove the unused Google Drive storage display-name flag, YAML field, list column, and metadata column.
• [documentation]: Make public guidance easier to navigate by removing repeated command-reference content and stale pre-release framing.
• [documentation]: Clarify Git LFS initialization and client credential-helper requirements, including platform-specific helper guidance.
• [tooling]: Validate Google Drive root folder IDs in configuration smoke tests after removing storage display names.
• [tooling]: Keep interactive storage smoke tests on their isolated gcloud fixture after removing the executable prompt.
• [tooling]: Add package scripts for building local release binaries for every supported target.
• [fixed]: Keep PAT-backed local LFS sessions valid until explicit or upstream revocation instead of requiring another GitHub PAT after eight hours.
• [fixed]: Refresh Google Drive access tokens after system sleep or a rejected storage request instead of failing migrations with HTTP 502.
• [fixed]: Accept server-canonical GitHub repository casing in migration upload action URLs.
• [fixed]: Replace opaque git credential fill failures with target-specific lfscloud login recovery while retaining the secret-safe underlying cause.
• [fixed]: Keep a configured LFS Cloud route out of legacy-source discovery when --server selects another address for the same repository.
• [fixed]: Accept Google Drive's canonical My Drive parent ID when creating or reusing the default .lfscloud folder.
• [fixed]: Expand a leading ~ in Google Drive gcloud configuration directories instead of nesting them below the server configuration directory.

LFS Cloud v0.2.6

• [changed]: Create or reuse an app-owned .lfscloud Google Drive folder during default storage setup.
• [fixed]: Expand a leading ~ in Google Drive client-secret paths before checking whether the file exists.

LFS Cloud v0.2.5

• [changed]: Create a missing private server configuration automatically whenever a command needs it.
• [changed]: Create missing parent directories for private server configuration automatically.

LFS Cloud v0.2.4

• [changed]: Store the default private server configuration under the platform's per-user config directory instead of directly in the home directory.

LFS Cloud v0.2.3

• [added]: Add arrow-key configuration menus for provider and repository setup.
• [added]: Infer interactive repository mapping IDs from the selected provider, owner, and repository.
• [added]: Select configured providers and removal targets from interactive menus.
• [added]: Automate isolated Google Drive authorization from a Desktop OAuth client JSON.
• [changed]: Resolve interactive GitHub repository IDs through authenticated GitHub CLI.
• [changed]: Let empty configurations use all server defaults without requiring a server: {} placeholder.
• [fixed]: Preserve custom Drive roots and ADC directories during provider reauthorization.
• [fixed]: Accept comment-only private configuration files as empty configurations.
• [fixed]: Accept valid GitHub repository names containing consecutive periods.
• [tooling]: Prevent Windows configuration smoke tests from invoking the real GitHub CLI instead of their isolated fixture.

LFS Cloud v0.2.2

• [added]: Generate durable-session encryption keys in the native credential store and add confirmed lfscloud sessions generate-key rotation that invalidates current sessions.
• [changed]: Hold an exclusive lifecycle lock for each metadata database so only one server can retain its sessions in memory and key rotation refuses to run while that server is active.
• [changed]: Listen on 0.0.0.0:15370 by default and infer Git LFS action URLs from each accepted connection, while retaining server.public_url for explicit hostname and proxy overrides.
• [changed]: Default GitHub repository providers to https://api.github.com so api_url is needed only for GitHub Enterprise or another override.
• [fixed]: Let configuration commands clear a stored GitHub API override and keep managed session-key bytes zeroed after use.
• [documentation]: Explain the credential exposure of plaintext LAN HTTP and the encrypted-tunnel but application-HTTP tradeoff for direct Tailscale access.

LFS Cloud v0.2.1

• [changed]: Load lfscloud.yml from the user's home directory by default instead of depending on the command's working directory.
• [fixed]: Prevent targeted Windows draft verification from failing under PowerShell StrictMode when exactly one release is selected.

LFS Cloud v0.2.0

• [added]: Preserve the legacy remote LFS URL in .lfsconfig so pulling the new target configuration does not prevent users from migrating remaining objects.
• [changed]: Authorize each user's GitHub identity and current repository permissions instead of sharing one server-configured GitHub account.
• [changed]: Reconcile and upload migrations through LFS Cloud so clients no longer need private server configuration or direct Google Drive access.
• [fixed]: Prevent fleet Windows verification from failing under SSH when Cargo, compiler, or nested smoke commands encounter rustup proxy links.
• [fixed]: Prevent Windows regression and smoke fixtures from failing before their intended assertions by consuming upload bodies and using current Basic action credentials.
• [fixed]: Let fleet Windows verification use the coordinator's active GitHub authentication without being rejected by an inaccessible inactive desktop credential.
• [fixed]: Reject stale migration config arguments, ignore the target as a legacy source, and validate server-issued upload actions before sending object bytes.
• [fixed]: Reject ambiguous fleet release resumes, surface remote validation failures, and repair missing Windows assets even after a green check.
• [fixed]: Validate the durable-session secret during config loading and count its documented minimum in characters.
• [documentation]: Group direct installers, Homebrew, WinGet, and checkout installation into compact README sections without advertising unavailable APT installation.
• [tooling]: Add one fail-fast fleet release command that fills missing Mac, Linux, and Windows checks, assembles the draft across both machines, and publishes the exact verified tag.
• [tooling]: Create the tagged draft before version verification so the native Windows continuation can start while macOS and Linux checks are still running.
• [tooling]: Save each aggregate verifier's output to its own retained log instead of terminal rolling windows, and purge verification logs older than 14 days.
• [tooling]: Generate required WinGet schema headers and update existing submission branches so requested manifest changes can be addressed.
• [tooling]: Resume failed Homebrew publication by trusting the configured tap and accepting its matching generated formula, and prevent duplicate WinGet upstream remotes.
• [tooling]: Publish a selected verified release without requiring a redundant typed publish vX.Y.Z confirmation.
• [tooling]: Skip Cloudsmith and APT distribution when no target is configured instead of blocking otherwise publishable releases.
• [tooling]: Keep publisher preflight failures visible after interactive release selection instead of clearing them with the terminal live region.
• [tooling]: Preserve trusted commit-status provenance when selecting publishable drafts so fully green releases are not omitted.
• [tooling]: Run final cross-platform release publication natively from macOS with Bash instead of requiring PowerShell or a clean worktree.

LFS Cloud v0.1.4

[0.1.4] - 2026-08-01

• [tooling]: Repeated local release commands now resume untagged version commits or reject an already-tagged HEAD, while failed or unpublished release notes roll forward until a version is published.

[0.1.3] - 2026-08-01

Version bump only.

[0.1.2] - 2026-08-01

• [fixed]: Prevent both Linux verifiers from writing Debian packages to a nonexistent /dist directory inside their reusable containers.
• [tooling]: Prevent persistent Linux verification target volumes from retaining several gigabytes of one-run Cargo incremental artifacts.
• [tooling]: Add checksummed direct-install scripts for macOS, Linux, and Windows, plus Homebrew, WinGet, and Debian package publication.
• [tooling]: Assemble and verify every platform asset in a GitHub draft, then publish it through a local interactive command as an immutable release with resumable distribution statuses.
• [tooling]: Releases now roll current changelog entries into a dated version section and use that section as the GitHub release description.

LFS Cloud v0.1.1

Full Changelog: https://github.com/Quicksaver/lfs-cloud/commits/v0.1.1