Skip to content

Release 0.9.0 rc.1

Jump to bottom
Nick Hamze edited this page Sep 4, 2026 · 1 revision

Fleet 0.9.0-rc.1 release record

Published September 4, 2026 at 15:03:55 UTC. Status: public GitHub pre-release. This is a staging/agency-pilot candidate, not general-availability certification. The existing stable release remains GitHub's “Latest” stable version.

Artifact and source

  • Release page · Download the plugin ZIP.
  • Source committed and pushed to Fleet main: 2057bc1bc49a8770c2472013d2d8ab1c0a9868de.
  • Installable asset: fleet-for-openstation.zip, 81,531 bytes, sixteen allowlisted runtime files. Do not install GitHub's generated source archive.
  • SHA-256: 2eeceeed274e3be3d1d0fc458d1475c0f20341553d1fe7ec180970f6114f2be5.
  • The published asset is the GitHub Linux CI build. It matches the locally built/tested ZIP byte-for-byte, and GitHub reports the same asset digest. The fetched release tag resolves to the source commit above.
  • An anonymous download from the public release URL matched the same checksum and passed ZIP integrity checks.
  • The earlier implementation report's checksum differs because release preparation added the two new screenshot descriptions to readme.txt; PHP, JavaScript and CSS are unchanged from that verified implementation.

Requirements and upgrade

WordPress 7.1+, PHP 8.3+, HTTPS, sodium, and OpenStation's experimental App Framework. The tested framework commit is 9bac9176b26a6228e3e57c9a7c8f11f586063afd; see Framework integration. No OpenStation source change, PR or merge was made.

Back up the hub database, files and salts before upgrading. Test the exact Fleet/OpenStation package pair on staging first. Fleet remains hub-only and uses Core Application Passwords and existing remote APIs. The source editor is not Gutenberg, durable autosave, an atomic lock or a backup system. The hosting/agency pilot gates still apply.

Included work

  • Native source editing, reviewed publishing/scheduling, Core revision comparison/recovery.
  • Saved per-site content views and compatible REST-enabled custom types.
  • Reviewed connection readiness, separate setup, and credential repair preserving agency details.
  • Fixes for dirty-window closure, stale health findings, timezone updates, malformed dates and connection metadata persistence.
  • Paginated collections, diagnostics, refreshed consumer README and ten real runtime screenshots.

See Modern Core and publishing for boundaries and regression details, Load testing for the earlier 10/20/30-site evidence, and Publishing visual review for the screenshot audit. The 30-site run was not repeated during release preparation.

Release verification

  • The release ZIP was installed on the disposable Studio hub and the full suite passed again: 28 tests, 0 failures, 0 skips, 1.8 minutes. This includes native accessibility checks, credential lifecycle, real content writes, publishing review, revisions, custom types and two dirty windows.
  • Cleanup preserved two demo connections and found no temporary E2E users or publishing items; the custom-type fixture was disabled.
  • Composer validation, coding standards, static analysis, compatibility checks, smoke/search tests and reproducible packaging passed locally. Composer and npm audits reported no advisories.
  • GitHub validation run: all four jobs passed—PHP 8.3 build, PHP 8.5 build/reproducibility, quality/dependency audit, and WordPress Plugin Check. Publication followed these gates.
  • A limited pre-publication pattern scan found no private keys, common provider-token forms or credential callback values in repository text. It is not a comprehensive security audit.

No WordPress.org upload or production-site deployment is part of this GitHub release.

Clone this wiki locally