Clickable table rows, showing details of every change. The panel will first show a quick overview of changes (for example, a list of updated properties) with the option to show a full diff which is a bit technical but displays all the details (for example, the option values).

UI for manual commits. This is useful in scenarios where VersionPress couldn't commit the change automatically, e.g., after a FTP upload or after a manual change.

Merge commits are visually marked in the main table.

Notification of new commits. If new commits are detected, a refresh link is displayed.

Times in the main table refresh automatically so they will now display correct time even if you don't refresh the page.

Other minor UI updates like an inline warning about the need to fully activate VersionPress or the explanation why commits done pre-activation cannot be undone / rolled back to.

Resolved db.php dependency. VersionPress no longer requires the db.php drop-in to be available, enabling compatibility with various caching, monitoring and other WordPress plugins. See also blog post with the details.

WordPress automatic background updates are no longer affected by VersionPress. In v1, if VersionPress was activated, WordPress stopped doing background updates. v2 maintains auto-updates if they were enabled before VersionPress activation.

Fixes / updates in automatic change tracking. Specifically:

The biggest one are translations which weren't tracked properly in v1.

Certain bulk changes now better report what has changed.

WordPress update is no longer a "commit everything" operation, we try to be more selective about it (as we are with other types of changes). Also, there were rare cases where WP update could have been tracked as other kind of update, e.g., an options update, which was fixed.

Some changes via the Customizer were not tracked correctly.

Improved menu change tracking.

Internal format update:

Options now use a multi-file storage as other entity types, lowering a chance of merge conflicts.

Certain special characters (backslashes, quotes) are stored differently now

The updates are not huge but mean that VersionPress 2.0 is not upgradable from 1.0 (or beta versions of 2.0) – see notes on that below.

New rollback implementation that works across merge commits.

Plugin compatibility is reported live in the plugins list. When VersionPress is running, it will add indicators in the main plugins table and in the search/install page, utilizing the white- and black-lists available since 1.0-rc3.

Major performance improvements during the initial activation. On some larger test sites, we saw dramatic improvements like the time necessary for the activation dropping down from 130 to 4 seconds. Large sites will always be a challenge when it comes to activation (because all needs to be indexed at once) but at least we now do the indexing as efficiently as possible, or very close to that.

Compatibility fixes for WordPress 4.3. Relatively minor but we've found and fixed a few issues around favicons and menu updates.