Changelog — Shopware Upgrade Radar

Every entry is a real change from the product's git history, dated the day it landed. Nothing here is a promise about the future. Entries before 0.3.0 carry no version number: the one-point-something milestone names used at the time were never released artefacts, and printing them beside 0.3.0 made the product look as though it had gone backwards. The version the product prints with --version is the only one that has ever shipped.

2026-08-20

Buyer-journey artifact rebuilt

Rebuilt the stale buyer-journey artifact so the acceptance suite and publish readiness read the same bytes a sale would ship.

2026-08-19

Report look migrated onto the brand theme

The HTML report now renders through the shared brand/report theme — consistent typography and styling across the product family.

2026-08-18

v0.3.0 — the buyer keeps the report

Every run now writes an HTML + Markdown report the buyer can keep, print and forward, and every finding says what to do next — including the honest "no compatible release exists; ask the vendor for a date".

Same day: the demo is now produced by running the product (a demo run is evidence, not an illustration), the shipped zip matches the source it was committed with, and a fleet-sweep typo that could mislabel every shop as conflicted was fixed and covered by a test.

2026-08-17

Renamed to "Shopware Upgrade Radar"

The product stopped being called "Preflight". The paid deliverable was rewritten to retire the earlier engagement framing, an MIT licence was added, and a buyer-journey acceptance suite (33 tests) was wired to the publish gate.

2026-07-16

The free hosted check

The free hosted checker went live: paste a composer.lock, get the per-plugin report server-side. No install, nothing stored (counters only).

2026-07-16

Release-availability lookup

A CONFLICT now splits into "fixable by plugin update" vs "genuinely blocking": the tool asks Packagist and the Shopware store whether a target-compatible release exists, and says honestly when it cannot answer.

2026-07-16

The core engine

The first working version: a declared-state reader (composer.lock + custom/plugins), a composer-semantics constraint evaluator, per-plugin verdicts with the excluding constraint quoted, a CLI with human and JSON output, honest limits, and a demo shop that exercises every verdict.

Not built (no dates promised)

An aggregated multi-shop roll-up — one report ranking every shop you manage. Today a run reads one shop; the install guide ships the loop that covers a fleet, and nothing is sold as a single-command sweep.
A sandboxed composer update --dry-run executor — the definitive check, run safely.

Anything shipped is an entry above with the date it landed, never a line here. The free hosted check and the release-availability lookup are shipped; they used to appear on this list as well, which told a visitor the reason to pay did not exist yet.

The source of this page is the product's git history. If you spot a change that is not listed, the fix is in the repo, not in a promise.