Skip to content

v0.9.0 release: bump version, restructure roadmap, sync Safari mirror#24

Merged
jakemgold merged 1 commit into
mainfrom
release/v0.9.0
Jun 7, 2026
Merged

v0.9.0 release: bump version, restructure roadmap, sync Safari mirror#24
jakemgold merged 1 commit into
mainfrom
release/v0.9.0

Conversation

@jakemgold

Copy link
Copy Markdown
Collaborator

Summary

The v0.9.0 release commit. Bundles everything that needs to be in the tree at the v0.9.0 tag.

Version bump

  • `package.json` and `manifest.json` → `0.9.0`
  • Xcode `MARKETING_VERSION` → `0.9.0` (was the default `1.0`)

The Safari container app version drops from `1.0` to `0.9.0` so everything reports the same number. The container isn't published anywhere users see, so the apparent regression is cosmetic.

Roadmap restructure (suggested in conversation)

Introduces a dedicated `v0.10.x` "store-readiness" phase between feature-complete (`v0.9.x`) and the v1.0 directory release. Rationale: separating "features done" from "store paperwork done" gives a stable share point before the actual store push, and the store-prep items deserve their own milestone (permissions audit, privacy policy URL, store listing copy, bundle ID coordination).

  • `v0.9.x` row → status: shipped. Trimmed to features + security + build; store-prep items moved out.
  • `v0.10.x` row → new. No new features. Captures the existing "Pre-1.0 gates" checklist.
  • `v1.0` → gated by v0.10.x completion (was: store-listing prep + WordPress Foundation alignment).
  • The "Pre-1.0 gates" section is renamed to "v0.10.x checklist" so the relationship is explicit.

Status line in README

Updated to refer to v0.9.x and name the v0.10.x phase.

Safari mirror sync reconciliation

Built `dist/` and synced Safari `Resources/` are brought into sync with the source tree. Some of these were drift from earlier PRs that omitted the synced Safari files per the lean-PR convention. The release commit is the right place to reconcile so a v0.9.0 clone is fully coherent.

Verification

  • Local sweep for `0.8.3` references — only ROADMAP historical note remains (about the Xcode rename shipping in v0.8.3, which is correct context)
  • `npm run package:chrome` produces `release/wordpress-browser-extension-0.9.0-chrome.zip` with `"version": "0.9.0"` in the bundled manifest
  • `npm run build:safari` syncs the new version into Safari Resources manifest
  • Xcode project parses cleanly (`plutil -lint`)
  • Chrome `chrome://extensions` reports the new version after reload (confirmed manually)
  • Safari container app reports the new version after rebuild (confirmed manually)

@jakemgold jakemgold requested a review from fabiankaegy as a code owner June 7, 2026 00:25
- `package.json`, `manifest.json`, and Xcode `MARKETING_VERSION` bumped
  from `0.8.3` to `0.9.0`. The Safari container app version dropped from
  the Xcode default `1.0` so everything reports the same number; the
  container isn't published anywhere users see, so the apparent
  regression is cosmetic.

- `ROADMAP.md` introduces two new phases between the shipped v0.9.x
  and the v1.0 directory release:

    - `v0.9.1` — targeted feature follow-ups: the Edit button for
      template-backed pages (#22) and the Safari toolbar icon
      full-color investigation (#15).
    - `v0.10.x` — store-readiness phase with no new features.
      Absorbs what was previously the "Pre-1.0 gates" checklist.

  Separating these keeps "remaining feature work" from "store paperwork"
  legibly distinct. The Pre-1.0 gates section is renamed to the
  v0.10.x checklist so the relationship is explicit.

- `README.md` status line refers to `v0.9.x` and names the v0.10.x
  store-readiness phase ahead of v1.0.

- Built `dist/` and Safari `Resources/` mirror brought into sync with
  the source tree so the tagged release state is fully coherent from
  a fresh clone. Some of these were drift from earlier PRs that
  omitted the synced Safari files per the lean-PR convention; the
  release commit is the right place to reconcile.
@jakemgold jakemgold merged commit b5c8063 into main Jun 7, 2026
@jakemgold jakemgold deleted the release/v0.9.0 branch June 7, 2026 00:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant