Fleet for OpenStation 0.10.0

Fleet 0.10.0 — one OpenStation desktop for every WordPress site you manage

Fleet for OpenStation 0.10.0 is the newest release for agencies and people who manage many independent WordPress sites. Install Fleet once on your OpenStation hub, connect each site through WordPress's own approval screen, and keep different sites open in clearly named, independent windows.

What this release adds

• A fleet-wide Inbox and Search for editorial, moderation, connection, and Site Health work.
• Saved client workspaces and reliable side-by-side site windows.
• Posts, pages, compatible custom content, authors, featured media, taxonomies, discussion settings, revisions, and reviewed publishing or scheduling.
• Bounded media uploads, comment replies, and reviewed bulk moderation.
• Opt-in encrypted draft recovery, conflict checks, unsaved-change protection, cache freshness, retry/backoff diagnostics, and repair actions.
• Explicit Reader, Editor, and Operator grants for hub teammates, with live server-side revocation.
• Explorer access to additional REST routes that the connected WordPress site already advertises, with confirmation before writes and deletes.

Fleet remains hub-only. Managed sites do not need a Fleet plugin, agent, or custom Fleet endpoint. WordPress Core REST APIs, capabilities, and revocable Application Passwords remain authoritative.

Requirements

Fleet 0.10.0 targets WordPress 7.1+, PHP 8.3+, HTTPS, sodium, and OpenStation's experimental App Framework.

Reliable saved multi-window identity currently requires the exact OpenStation build from PR #763, commit a48d37b8bfdc6453056eb9345ff610c396a71e15, until a released OpenStation package contains that fix. The upstream PR remains open. A fresh 48–72-hour endurance run, independent-hosting trials, and agency onboarding pilots remain operational-hardening work.

Back up the hub database, files, and salts, then test the exact Fleet/OpenStation pair on staging. Install the attached fleet-for-openstation.zip, not GitHub's generated source archives.

Verification

• Final source commit: 6b7c8242fc160afeafd45a5ddcf92201777e100a.
• Plugin ZIP SHA-256: af0f70a17af9cf8906cbb72f883a1e18502665639c1ac48863c5b5e97d1618d8.
• The final hosted validation covers PHP 8.3/8.5, reproducible packaging, code quality and dependency audits, WordPress Plugin Check, a real upgrade from 0.8.0, clone restore, real browser mutations and isolation on Chromium/Firefox/WebKit, and saved multi-window identity.
• Local reliability work additionally exercised 30, 50, and 100 independent WordPress origins across MySQL and MariaDB. These measurements are evidence, not production performance guarantees.

Start with the consumer README, then use the getting-started guide, current capability map, security model, screenshots, and reliability evidence.

Fleet for OpenStation 0.9.0-rc.1

Fleet 0.9.0-rc.1 brings everyday publishing work into each connected site's native OpenStation window.

This is a pre-release for staging and agency pilots, not a general-availability release. Requires WordPress 7.1+, PHP 8.3+, HTTPS, sodium, and an OpenStation build with the experimental App Framework. The tested framework commit and setup details are in the wiki.

What's new

• Create and edit HTML/WordPress block source without opening another wp-admin.
• Review the destination, publishing time, and changes before publishing or scheduling.
• Compare Core revisions and recover supported source fields into the editor before saving.
• Save per-site content filters and discover supported REST-enabled custom content types.
• Review connection readiness, finish setup separately, and repair revoked credentials without losing client details.
• Use smaller paginated collections and redacted local support diagnostics.
• Refreshed native layout, accessibility checks, consumer README, and ten real screenshots.

Reliability fixes

• Closing a dirty window asks before discarding edits; two site windows remain independent.
• Failed or partial Site Health checks retain last-known findings and clearly mark stale results.
• Timezone changes use and verify Core's correct REST field.
• Malformed scheduling dates fail validation cleanly.
• Connection updates preserve new metadata defaults, and uncertain content creation is not automatically replayed.

Before installing

Install Fleet only on the hub. Managed sites use existing Core APIs and revocable Application Passwords; no new Fleet endpoint or client-site Fleet plugin is required. No OpenStation source changes were made.

Back up the hub database, files, and salts before upgrading. Start on staging with the verified framework build. The editor is source-based, not Gutenberg; it is not durable autosave, an atomic remote lock, or a backup system. Public-host compatibility and agency pilots remain launch gates.

Download fleet-for-openstation.zip below, not GitHub's automatically generated source archives.

SHA-256: 2eeceeed274e3be3d1d0fc458d1475c0f20341553d1fe7ec180970f6114f2be5

Setup and operating guide · Release verification

Fleet for OpenStation 0.8.0

Fleet 0.8.0 makes the native OpenStation fleet experience faster and safer as agencies add more sites.

Highlights

• Keeps each site in its own independent OpenStation window, with no classic wp-admin fallback.
• Stores compact connection records separately and loads bounded search indexes only when needed.
• Updates search incrementally with paginated reconciliation instead of rebuilding an entire fleet on demand.
• Runs status, metadata, search, and health synchronization on separate cadences with a resumable 40-second work budget and automatic backoff.
• Protects reconnect, disconnect, cron, and manual-refresh races with per-user leases, connection generations, and revision-aware search writes.
• Isolates hub data correctly on WordPress Multisite, including safe first-hub migration from earlier storage.
• Hardens remote responses, credentials, cleanup reporting, and API Explorer method validation.
• Adds short-lived read caching and duplicate-action/window protection while preserving independent windows.
• Adds deterministic release archives, four-way version checks, static analysis, WordPress Coding Standards, PHP 7.4 compatibility checks, dependency audits, and two-site browser/accessibility tests.

Requirements

• WordPress 6.5 or newer
• PHP 7.4 or newer
• HTTPS
• A current OpenStation build with the experimental App Framework on the hub

Validation

• GitHub CI: PHP 7.4 and PHP 8.5 builds, reproducibility, static quality, and WordPress Plugin Check
• Two-site Studio E2E: 5/5 passed with independent Harbor Arts windows
• Zero console/page errors and zero WCAG A/AA Axe violations
• All ten managed-site sections and safe API Explorer GETs passed on both connected sites
• Reproducible ZIP SHA-256: 16c4587da8fcaa9a7aa25c688a77a47cf67fc8284f71c6d9f0531d7791e55f0f

Fleet for OpenStation 0.5.1

Fleet 0.5.1 ships the polished OpenStation-native interface and refreshed screenshots. It unifies button geometry across native buttons, links, and connection summaries; optically aligns button icons; and bumps the plugin asset version so existing browsers load the corrected stylesheet.

Fleet for OpenStation 0.1.2

Makes the managed-site authorization flow work from inside the OpenStation Fleet window by opening approval at the top browser level.\n\nVerified in WordPress Studio with Fleet running as an OpenStation window: connect, approve, return to the hub shell, and display the connected site's active OpenStation version.

Fleet for OpenStation 0.1.1

Corrects Application Password callback encoding so Fleet retains its state and nonce through the managed-site approval flow.\n\nVerified end to end in WordPress Studio: connect, credential introspection, missing-plugin detection, remote OpenStation 1.1.5 installation and activation, status refresh, disconnect, and Application Password revocation.

Fleet for OpenStation 0.1.0

Early preview of Fleet for OpenStation. Install the ZIP on the WordPress site that will act as your hub, then connect managed sites with WordPress Application Passwords.\n\nThis preview supports site discovery, connection status, OpenStation detection, and remote OpenStation install/activation.