-
Notifications
You must be signed in to change notification settings - Fork 100
Release Changelog Draft
This is the first pre-release of v0.6.0. It includes 12 closed issues and 18 merged pull requests (aside from dependency updates including updating Workbox to v5.1.4).
For a full list of issues and pull requests, see the 0.6 milestone. Compare all changes in 0.5.0...0.6.0.
- ✨ Add default caching strategies for navigations and assets from core, themes, plugins, and uploaded images. This, along with the UI to opt-in for offline browsing (below), eliminates the need for having a separate helper plugin to make a site available offline. https://github.com/GoogleChromeLabs/pwa-wp/pull/338, https://github.com/GoogleChromeLabs/pwa-wp/issues/265, https://github.com/GoogleChromeLabs/pwa-wp/issues/176, https://github.com/GoogleChromeLabs/pwa-wp/issues/264
- ✨ Provide means of opting-in to offline browsing via a new toggle on the Reading Settings screen. https://github.com/GoogleChromeLabs/pwa-wp/issues/344, https://github.com/GoogleChromeLabs/pwa-wp/pull/365
- ✨ Add
offline.php
template for the Twenty Twenty-One theme. https://github.com/GoogleChromeLabs/pwa-wp/pull/361 - Use pretty permalink for frontend service worker, using
/wp.serviceworker
instead of/?wp_service_worker=1
. https://github.com/GoogleChromeLabs/pwa-wp/issues/287, https://github.com/GoogleChromeLabs/pwa-wp/pull/289 - Fix support for serving 304 Not Modified service worker script responses. https://github.com/GoogleChromeLabs/pwa-wp/pull/291
- Update wording of the server offline message. https://github.com/GoogleChromeLabs/pwa-wp/pull/314
- Avoid constructing asset versions with HTML entities in context of SW. https://github.com/GoogleChromeLabs/pwa-wp/pull/325
- Correct version handling for precached assets. https://github.com/GoogleChromeLabs/pwa-wp/pull/317
- Eliminate use of
wp_service_worker_json_encode()
. https://github.com/GoogleChromeLabs/pwa-wp/issues/341, https://github.com/GoogleChromeLabs/pwa-wp/pull/359 - Update the way a navigation route is registered (for single page apps). https://github.com/GoogleChromeLabs/pwa-wp/issues/319, https://github.com/GoogleChromeLabs/pwa-wp/pull/320
- Add
X-Robots-Tag
to service worker response for good measure. https://github.com/GoogleChromeLabs/pwa-wp/issues/300, https://github.com/GoogleChromeLabs/pwa-wp/pull/330 - Guard against scripts and styles being erroneously printed in service worker at the
wp_enqueue_scripts
action. https://github.com/GoogleChromeLabs/pwa-wp/issues/293, https://github.com/GoogleChromeLabs/pwa-wp/pull/336
- Serve web app manifest as
application/manifest+json
. https://github.com/GoogleChromeLabs/pwa-wp/issues/306, https://github.com/GoogleChromeLabs/pwa-wp/pull/349 - Add helper function to obtain the URL for the Web App Manifest. https://github.com/GoogleChromeLabs/pwa-wp/pull/305
- Allow HTTPS detection and UI to be disabled. https://github.com/GoogleChromeLabs/pwa-wp/pull/308
- Mark all classes as
final
. https://github.com/GoogleChromeLabs/pwa-wp/issues/340, https://github.com/GoogleChromeLabs/pwa-wp/pull/360 - Eliminate Travis in favor of GitHub Actions for linting and testing. https://github.com/GoogleChromeLabs/pwa-wp/issues/197, https://github.com/GoogleChromeLabs/pwa-wp/pull/354
- Migrate default branch name from
master
todevelop
. https://github.com/GoogleChromeLabs/pwa-wp/pull/296
Alberto Medina (amedina), Alejandro Vargas (avargaz), Daniel Olson (emaildano), Derek Herman (derekherman), Erick Hitter (ethitter), Felix Arntz (felixarntz), Gary Jones (GaryJones), Hidetaka Okamoto (hideokamoto), Ian Dunn (iandunn), Jono Alderson (jono-alderson), Koen Van den Wijngaert (vdwijngaert), Kurt Zenisek (KZeni), Pascal Birchler (swissspidy), Piotr Delawski (delawski), Weston Ruter (westonruter)
You can install the pwa.zip
build linked below by uploading it in the WordPress admin.