Skip to content

Release 1.11.0: connect through Scanfully's OAuth server - #65

Merged
barrykooij merged 6 commits into
mainfrom
dev
Nov 12, 2026
Merged

barrykooij merged 6 commits into
mainfrom
dev

Conversation

@barrykooij

Copy link
Copy Markdown
Member

The plugin's part of Scanfully Connect on the OAuth server (api#354).

  • Connect: connecting a site goes through Scanfully's authorization server, where the user picks the site and chooses what Scanfully may do on it. Reading site data is always included.
  • Change what Scanfully may do: a button on the settings page asks for new permissions; cancelling keeps the current connection.
  • Move by itself: a connection from before 1.11 moves to the OAuth server at its next token refresh check (the hourly jobs), with no reconnect. If the server cannot take it over yet, the plugin keeps refreshing on the legacy route and tries the move again a day later.
  • Signed sync requests: when Scanfully asks the site to sync, it signs the request (RS256), and the plugin checks it against the keys at api.scanfully.com/.well-known/scanfully-plugin-keys.json, kept for a day.
  • Readme: WooCommerce checkout monitoring is described as an add-on instead of a beta; the connect FAQ and External services describe the new flow.

PHP error monitoring is not part of this release; it follows in its own release.

Release this any time: the API side (v2.6.0, OAuth mode since v2.6.1) has been live since 4 November 2026 and accepts old and new plugins alike.

  • Merge with a merge commit, then publish release 1.11.0, which puts it on wordpress.org.
  • If the release is not on 12 November 2026, change the date in the readme changelog first.

Tested

  • composer qa: lint and PHPStan clean, 688 unit tests pass.
  • End to end on a database copy with two wp-env sites (1.11 and the released 1.10), in both API connection modes: connect, permissions, signed sync with replay and forgery refused, refresh, change access cancel and approve, disconnect, and the move from 1.10.
  • Local test plans on Valet sites, including a 1.9.1 site with 60-character tokens moving through its grant and a rollback of the API to the legacy mode.
  • Canary on production, 12 November 2026: this build on two live sites, one of them coming from 1.9.1. Both moved their connection to the OAuth server by themselves (the second at its next site health job), kept reporting with the new tokens, and accepted signed sync requests from "Sync sites" in the dashboard. No errors in the API logs.
  • Not tested: multisite and translated sites.

…oice of what Scanfully may do, moves an existing connection there by itself, and takes requests Scanfully signs for the site
…shing on the legacy route before its token expires
…l the new one is approved, so cancelling leaves the site connected
@barrykooij
barrykooij merged commit cf30bff into main Nov 12, 2026
16 checks passed
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