Skip to content

v1.0.0-rc1 — Release candidate for 1.0

Pre-release
Pre-release

Choose a tag to compare

View all tags
@jakemgold jakemgold released this 24 Jul 18:24
v1.0.0-rc1
ecbf9e2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

A newer release candidate is available: v1.0.0-rc2. It folds in the QA-pass fixes from #76; test that build instead.

Release candidate for 1.0. Functionally identical to v0.11.2: the only change is internal preparation for Apple App Store distribution — the Safari app and extension bundle identifiers moved from the original developer's namespace to org.wordpress.browserextension, under the WordPress Foundation Apple Developer account (#72). No behavior, permission, or Chrome-side changes.

Anyone who installed a previous Safari build will see the old extension listed alongside the new one, since macOS treats the new identifier as a new extension. Deleting the previously built app removes the leftover; see SAFARI.md.

Barring further issues found in this candidate, 1.0.0 final ships from this build plus one addition found while preparing the App Store submission: an export compliance declaration in the Safari app's Info.plist (#74). That key is submission metadata for App Store Connect and has no runtime effect, so the builds below remain accurate for testing.

Install

  • Chrome / Chromium: unzip wordpress-browser-extension-1.0.0-chrome.zip and load it unpacked at chrome://extensions.
  • Safari (macOS): unzip wordpress-browser-extension-1.0.0-safari.zip and move the app to Applications. It is ad-hoc signed, so Gatekeeper shows a warning on first launch. See SAFARI.md.
Assets 4
Loading