Shipper 1.0.0 Beta 5

The fifth beta removes the last CLI instructions from the dashboard and adds a first-run restore flow plus full app tokens.

Technical version: 1.0.0-rc.26. It updates automatically from 1.0.0-rc.25 on the Main channel.

Load a save

• Settings > Recovery no longer prints a restore command. Load a save explains the fresh-install flow and keeps the archive and key exports next to it.
• The first-run screen offers Restore a save: setup token, instance archive, recovery key, a destructive warning and restart progress.
• Shipper validates the archive, stages it under the data directory and restarts. The next start installs it before the database opens, removes the setup token, and starts with applications stopped and schedules disabled.
• Restore runs on a fresh install only, so live applications are never rewritten underneath. The setup endpoint is setup-token protected, size limited and rate limited, and extends the read deadline for large archives.

Access tokens

• New Full app access scope covers settings, environment, command bodies, secret reveals, domains, releases, backups, tasks and deletion.
• Full tokens keep host maintenance explicit. Administration, terminals and instance recovery stay interactive, and app-scoped tokens stay limited to their applications.
• Existing scopes are unchanged.

Verification

• 21 web unit tests, 20 browser tests, and the Go httpapi, store and deploy suites.
• New tests cover restore guards, staged restore application, full token access, command visibility and scope boundaries.

Shipper 1.0.0 Beta 4

The fourth beta replaces the last native controls and brings the landing current.

Technical version: 1.0.0-rc.25. It updates automatically from 1.0.0-rc.24 on the Main channel.

Controls

• Selects and checkboxes now use one non-native control system.
• Selects open a portalled listbox with the current option checked, full keyboard support, and aria-expanded, aria-controls and aria-activedescendant.
• The menu snaps to about 75% of its height, then eases out the last quarter to settle.
• Checkboxes are 16 px raised squares with a near-white checked fill, a spring-in check and a press state.
• Row action menus such as the Users ... menu portal out of the table, focus the first item, support arrow keys and return focus on close.
• Touch devices keep the platform picker.

Landing

• The "Deploy anything." section leads with the quick new-application screen.
• The first visit opens through the Shipper mark with an ease-out cut-out.
• The installer redirect is forced to the Main channel.

CI

• The browser job installs Chromium without the optional apt font set, so a mirror outage cannot fail the run.

Shipper 1.0.0 Beta 3

The third beta focuses on the first five minutes and the launch surface.

Technical version: 1.0.0-rc.24. It updates automatically from 1.0.0-rc.23 on the Main channel.

First-run

• The installer now prints a short host plan, timed progress lines and a clear success block.
• The success block shows the dashboard URL and the 30-minute setup token, with instructions for the first-run form, rotate-claim and terminal claim.
• Fresh installs wait briefly for the setup token and fall back to its file path if needed.

Recovery

• Recovery is restructured into latest copy, off-server storage, recovery tools, scheduled backups and history.
• Recovery key and restore are full-width rows instead of overlapping controls.
• The restore command and its consequences stay inside the expanded row.
• The mobile layout stacks each fact cleanly.

Landing

• Every product screenshot is refreshed with current UI and realistic mock data.
• Users and Authentication surfaces are included.
• The landing has canonical metadata, Open Graph, Twitter cards, JSON-LD, robots, a sitemap and a 1200 x 630 social image.
• The dashboard rounded-square favicon is used throughout.
• /install.sh has redirects for Netlify, Cloudflare Pages and Vercel plus a static fallback.

The full collaboration and authentication work from Beta 2 remains included.

Shipper 1.0.0 Beta 2

This patch follows Shipper 1.0.0 Beta 1 with the settings CSRF fix.

Technical version: 1.0.0-rc.23. It updates automatically from 1.0.0-rc.22 on the Main channel.

Fixes

• User creation, role changes, account disable and enable, removal, password resets, password removal and factor reset now send the session CSRF token.
• Password policy and provider save, remove and test requests now send it too.
• Added a browser regression test that provisions a user and saves provider settings through the real UI.

The full collaboration release from Beta 1 remains included: administrator-provisioned accounts, Admin, Developer and Viewer roles, Google, GitHub and Discord sign-in, verified-email linking, temporary-password gates, Shipper TOTP enforcement, audited account changes and the split-video authentication screens.

Shipper 1.0.0 Beta 1

The first Shipper beta. This build brings the collaboration model, provider sign-in and the redesigned authentication experience together into the most complete Shipper yet.

Technical version: 1.0.0-rc.22. It stays on the existing rc ladder so Main-channel installations update automatically from rc.21.

Highlights

• Administrator-provisioned accounts with Admin, Developer and Viewer roles.
• One implicit workspace, with no public signup or OAuth account creation.
• Email and password, Google, GitHub and Discord sign-in configured independently.
• Verified-email identity linking, stable provider IDs and one account across every method.
• Temporary-password gates that follow the account across password and provider login.
• Shipper TOTP after every password or provider sign-in, including enforcement against existing sessions.
• Settings pages for Users and Authentication, with sealed provider secrets, exact callbacks and return-to-Shipper tests.
• Split-video sign-in, first-admin setup and onboarding screens with the same shell as the application.
• Explicit server-side role isolation across application mutations, secrets, terminals, backups and administration.

Upgrade

Use the Main update channel in Settings. Existing 1.0.0-rc.21 installations can update in place and keep their applications, releases, accounts, factors and provider identities.

Provider sign-in needs real Google, GitHub or Discord OAuth credentials and the callback shown in Settings > Authentication.

Verification

• Go unit and integration tests pass across all packages.
• 21 web unit tests pass.
• 17 browser tests pass.
• Collaboration and authentication screens are captured against the real backend.
• CI, browser and production image checks passed before the release.

v1.0.0-rc.21

1.0.0-rc.21 (2026-11-09)

Features

• add liquid-glass mobile bottom navigation (#48) (c244d2f)
• add simple application creation with the original manual wizard (#42) (57352f0)
• first-class databases, networking and service terminal (#45) (d7b6e3b)
• ship the polished Shipper landing page (#44) (19e0208)
• show deployment history for database resources (#46) (68931cb)

Bug Fixes

• simplify application overview and surface resource usage (#47) (474ec20)

v1.0.0-rc.9

1.0.0-rc.9 (2026-11-07)

Features

• distribute control-plane updates (#17) (21216ad)

v1.0.0-rc.8

1.0.0-rc.8 (2026-11-07)

Features

• connect GitHub organization repositories (#14) (adda47a)
• provide internal database connection strings (#15) (ed96425)

Bug Fixes

• handle GitHub repository loading and account switches (#13) (fa3de98)
• send Discord-compatible webhook notifications (#12) (8708de6)

v1.0.0-rc.7

1.0.0-rc.7 (2026-11-07)

Features

• report the running version from the health endpoint (#5) (d64c8c5)

v1.0.0-rc.20

1.0.0-rc.20 (2026-11-07)

Bug Fixes

• remove settings group icons (#40) (d3e3e6c)