Full explainer available here
When a new version of a piece of native software rolls out users are typically made aware through a notification in their operating system or the app store they use. The web—in contrast—is evergreen, meaning that software built atop it is always up to date. Because of this, there is no formal “moment” in which developers of web-based software can inform their users of what’s changed with their software from release to release (e.g., new features that have been added, which bugs have been fixed). Providing a standardized means of surfacing version history would enable developers to surface this useful—and sometimes crucial—information.
In the existing manifest.json this proposal would add a new subtree that contains information about where the PWA developer presents new changes to the PWA.
If the developer decides they want to leverage this feature, they would include the relevant information in their manifest.json and user agents would present this information.
The specifics and syntax of the proposal are available in the explainer linked above.