Repository navigation
Ghost FTP 0.99.74 Preview
Pre-releaseGhost FTP by Brendigo — 0.99.74 Preview
Source work: 21–22 November 2026 · Distribution channel: Preview
Additional Windows network transfer verification
The Windows native protocol job now runs the existing real FTP upload/download integrity suite against a loopback-only test server. It exercises connection, multi-size upload/download verification, zero-byte and Unicode filenames, rename collision safety, listing, removal and failure behavior. Its result is required by the protocol security gate, in addition to Linux FTP/FTPS/SFTP and Windows local filesystem checks. This change does not establish native Windows FTPS or SFTP network interoperability, cloud-provider credentials, or exhaustive user-interface functionality. Those remain explicit follow-up acceptance requirements.
Restored automatic Preview release promotion
- Verified the last published
v0.99.73release workflow did not requiremain.protected=true, while a later source-only hard gate madev0.99.74fail despite successful current-main quality/protocol/native/hardening checks. - Replace the overly restrictive protection-only gate with two fail-closed provenance options: protected main, or one exact merged GitHub PR into the canonical main branch matching the release source commit. Unmerged or wrong-repository PRs and arbitrary direct pushes cannot authorize publication.
- Keep exact-main SHA, all existing release CI gates, immutable published predecessor, installer format/inventory and checksum verification untouched. This change does not assert that a new GitHub Release has already been published.
- Track enabling GitHub branch protection as a separate defense-in-depth repository-owner task in issue #320.
Safer queued overwrite confirmations
- Assign each pending file-conflict dialog a unique monotonic identity, even when multiple transfers share the same path and remaining-item count.
- Bind the dialog's React key and confirmation/cancellation callback to that identity. Discard duplicate clicks, stale Escape handlers, and delayed events from an earlier dialog instead of accidentally applying that decision to the next pending conflict.
- Add deterministic tests executing the actual conflict-store source with duplicate prompt names, repeated callbacks, invalid IDs, and UI identity contracts; include them in the mandatory frontend quality gate.
- Repair a release-governance test syntax error found by GitHub Actions on the first PR #322 head; require a fresh successful exact-head result before merging.
- These changes prevent unintended overwrite decisions. The separate verified merged-PR release path preserves full source, protocol, metadata and package integrity checks.
Safer transfer conflict handling and release diagnostics
- Fix the Transfer Center's Remember my choice as the default behavior for existing-file conflicts: the selected overwrite, rename or skip decision now takes effect for remaining collisions in the currently queued batch, even without a separate Apply to all checkbox. Previously the UI persisted the choice but still asked again for subsequent conflicts within the same batch.
- Update the in-flight batch policy after remembering a choice so later source items use the selected safe backend overwrite policy. The default is written once rather than redundantly for every conflict.
- Preserve fail-closed behavior when destination listing fails: do not enqueue a potentially destructive batch without checking existing targets.
- Add tests that exercise the actual production batch code for remembering overwrite/skip, batch-local apply-to-all rename, cancel, destination listing failures and silent-mode duplicate-name prevention.
- Improve release failure diagnostics to link branch-protection hardening issue #320 instead of deleted historical #302. Existing quality, protocol, Windows/Linux native and artifact verification remains mandatory; exact merged-PR provenance is a supported alternative to server-side protection.
- These are source changes for unpublished 0.99.74 Preview. Only successful exact-head CI, authenticated release source provenance and verified published assets can establish a real distributable release.
Transfer Center history workflow improvements
- Add rolling Last 7 days and Last 30 days selectors beside existing last-hour and last-24-hours history filters, with inclusive boundary handling and future/invalid timestamp exclusion.
- Refresh history filters each minute only while a time window is selected; stop the timer when the filter is cleared or the view unmounts, so idle transfer histories don't remain frozen and normal queue views avoid unnecessary wakeups.
- Verify weekly/monthly timestamps, combined status and direction filtering, non-mutating results, and interval cleanup contracts through the UI quality workflow. This changes only history presentation, never persisted transfer records or server files.
Transfer throughput accuracy and native Windows concurrency
- Preserve accumulated byte deltas across sub-40ms backend progress bursts so the Transfer Center and status bar no longer discard earlier updates when calculating instantaneous rates.
- Stop refreshing stale samples during insufficient sampling intervals; hide invalid, backwards-time and non-finite telemetry rather than displaying misleading transfer rates.
- Add executable regression tests for bursty callbacks, stalled transfers, clock rollback, retry counters and malformed telemetry. They are part of the UI CI gate; the source fix requires a successful exact-head run before acceptance.
- Extend the existing live Windows FTP integration suite to cover 1, 4 and 8 independent parallel upload/download sessions, with full SHA-256 equality and repeated execution. PR #319 was merged only after quality, Windows/Linux native build, hardening and protocol E2E workflows succeeded. Windows FTPS/SFTP and interruption tests remain open.
Highlights
- Prevent repeat execution of confirmation and prompt actions caused by rapid double-click/Enter events before React can render the busy state.
- Consolidate the desktop confirmation dialog with the reusable file-ui dialog while preserving error toasts in the desktop app and inline error feedback for the shared component.
- Remove duplicate Escape handling from the file prompt and prevent implicit form submission.
- Hold the single-flight guard through successful dialog dismissal and release only on action failure, with additional source regression checks.
- Share the accessible focus-management hook between desktop workspaces and the file browser without changing keyboard-navigation policy.
- Remove two unused Tauri JavaScript dependencies (
@tauri-apps/plugin-fsand@tauri-apps/plugin-shell) and their lockfile records, leaving needed native backend APIs untouched. - Strengthen the Rust dead-code scanner for nested block comments, raw strings and quoted characters, including new regression fixtures.
- Extract the Agent Bridge's 400+ lines of Rust regression tests from
bridge.rsintobridge/tests.rs, keeping the same tests linked into the same module. - Report truthful HTTP status reason phrases (e.g., 404 Not Found and 502 Bad Gateway) instead of presenting failed Agent Bridge operations with an
OKreason. - Reject invalid, oversized and inconsistent base64 file replies from paired Agents instead of silently turning them into empty success responses; correct the Agent daemon read-file truncated flag for an exact-length file.
- Update source-level interaction regression checks.
- Correct the published v0.99.73 predecessor and align active documentation with v0.99.74 source.
- Improve the public README's presentation and historical native screenshot provenance.
- Keep the EULA/LICENSE distribution addendum consistent with the current source version and add a legal review checklist.
- Document required native Windows/Linux reference comparison and a narrowly scoped duplicate-code/dead-code audit.
Compatibility and user data
No intentional changes were made to FTP/FTPS/SFTP wire protocols, connection profiles, credential storage, file-transfer persistence, remote path handling or updater verification. This source update is not evidence of identical runtime behavior on all servers or operating systems.
Verification and outstanding requirements
- Mandatory exact-head GitHub Actions quality, native Windows/Linux builds, security gates and FTP/FTPS/SFTP protocol E2E must pass before merge/release. A source-level contract is not a full behavioral test.
- Native confirmation, keyboard, accessibility and destructive-operation QA remains required.
- 1:1 visual reference parity remains unverified until actual version-matched, OS-matched captures are compared to approved sources.
- Current README images are verifiable real earlier-build captures, not images of a new 0.99.74 binary.
- GitHub returns HTTP 410 for the historical deleted protection issue #302. Active replacement #320 remains open. Main branch protection was still disabled on 22 November 2026; verified exact merged-PR provenance now provides an alternate release authorization while server-side protection remains recommended.
- Qualified legal review remains required before claiming the licence has been professionally approved.
- The existence of these source notes is not proof that a signed release has been published.
See targeted audit, visual acceptance and legal review.
Linux installation: choose the correct Ghost FTP package
Platform: Linux x86_64 / amd64. These are package-family labels, not
certifications that every distribution/version has been tested. The native
Windows/Linux build currently runs on an Ubuntu 22.04 x86_64 GitHub runner;
installed-device checks across other distributions remain required.
| Linux edition in GitHub Releases | Intended distribution / installation family | Important prerequisite |
|---|---|---|
GhostFTP-Linux-amd64-v<VERSION>.deb |
Debian, Ubuntu, Linux Mint, Pop!_OS, and compatible Debian-family amd64 systems | APT/dpkg dependencies, WebKitGTK 4.1 and compatible GTK/GLib; test on the target distro release. |
GhostFTP-Linux-x86_64-v<VERSION>.rpm |
Fedora, openSUSE, RHEL-compatible RPM-based x86_64 systems | RPM runtime dependencies, WebKitGTK and GTK availability differ. Package format alone does not prove the build launches. |
GhostFTP-Linux-x86_64-v<VERSION>.AppImage |
Portable / cross-distribution candidate for many glibc-based x86_64 desktop systems | Check FUSE/AppImage runtime, compatible glibc, WebKitGTK/GTK libraries and display server. Not guaranteed universal. |
GhostFTP-Linux-x86_64-v<VERSION> / .tar.gz |
Manual / advanced installation on compatible x86_64 desktop Linux | Not statically linked; administrators must supply all system runtime dependencies and desktop integration. |
Replace <VERSION> with the exact published tag number. Verify
GhostFTP-v<VERSION>-SHA256SUMS.txt before executing installers. A SHA-256
checksum only verifies integrity against that manifest; it does not prove
publisher identity or replace a cryptographic code signature.
No native package is currently built for Linux ARM64/aarch64,
32-bit x86, musl-only Alpine, or every NixOS/immutable-container configuration.
Arch Linux, Manjaro, EndeavourOS, Gentoo, elementary OS and others may be
candidates for AppImage/manual installation, but are not certified based
solely on an Ubuntu runner. Check compatible dependencies first; do not force a
Debian RPM/DEB package onto an unrelated distribution. On Wayland systems,
GTK/WebKit or XWayland availability can affect behavior.
Required acceptance before claiming distribution support
For each distribution and version named as tested, record its exact image
version, x86_64 architecture, display protocol (X11/Wayland), WebKitGTK/GTK
versions, GNOME Keyring/KWallet state, and the native binary hash. Verify:
- Install, first launch, File Manager/Sites/Transfers/Settings/Sync navigation,
resize at 1290×852 and 480×600, and correct keyboard focus. - FTP warning, verified FTPS TLS and SFTP SSH host-key checks on actual
endpoints; failed identity checks must not connect. - Queue retry/cancel, interrupted upload/download preservation, symlink and
overwrite safety, and shutdown/restart without losing profile metadata. - OS-backed credentials with locked and unavailable Secret Service; no
plaintext fallback or secret-bearing logs. - Uninstall and reinstall without silently deleting stored user documents,
connection profiles, or keys.
Current GitHub Actions Linux QA produces real Xvfb/WebKit screenshots of
seven core workspaces, not mockups. Those captures prove native rendering under
the CI environment; they do not certify a GNOME/KDE/Wayland distro or pixel
parity with all 29 user-supplied Linux design references.
Related: Linux handbook ·
Native desktop build ·
Published releases.
Operational prerequisites for unsigned desktop builds
Running the native binary does not require a purchased signing certificate. Verify the SHA-256 checksum of your package against the matching official release manifest; this validates file integrity, not cryptographic publisher identity. Saved credentials require an unlocked Secret Service provider and the secret-tool client (the DEB declares libsecret-tools, the RPM declares libsecret). An unavailable vault is a blocking error, not a reason to store plaintext passwords. Before upgrading, create an encrypted backup and ensure all transfers are finished. The desktop Updates screen offers the complete GitHub Releases index because signed auto-updates and manually downloadable package editions are independent.