feat(updates): [SITE-5883] Add dismiss option to WordPress update notice

[mehta-asim]

Summary

• Make the "A new WordPress update is available!" notice dismissible. The notice already carried the is-dismissible class, but WordPress's native dismiss is client-side only, so the notice returned on the next page load (the GitHub Add option to dismiss WordPress update notice in the admin dash #116 complaint).
• Persist dismissal per user, keyed to the available WordPress version via a single user-meta key (pantheon_dismissed_update_notice). A newer available version no longer matches the stored value, so the notice returns automatically. No stale-meta cleanup needed (one key, overwritten).
• Add a wp_ajax_pantheon_dismiss_update_notice handler (nonce + update_user_meta; the target version is resolved server-side, not trusted from the client) and a small script that fires on the native dismiss click.
• Add a render gate to _pantheon_upstream_update_notice() that skips the notice when the user's dismissed version equals the current available version.

Context

SITE-5883

Community feedback (GitHub #116): the update notice is persistent and reappears on every admin page load. Maintainer guidance on that issue confirmed the fix must use user meta keyed to the version (client-side is-dismissible alone does not persist).

Builds on SITE-5884 (#119, merged): reuses the _pantheon_render_notice() dismissible support and the playwright-bdd e2e harness. _pantheon_render_notice() and the other dismissible callsites (multisite-finalize, page-cache) are intentionally left untouched — persistence is wired only at the update-notice callsite.

Changes

File	Change
inc/pantheon-updates.php	Render gate + dismissible => true on the update-available notice; wp_ajax_pantheon_dismiss_update_notice handler; enqueue + localize; two shared consts
inc/assets/js/pantheon-update-notice-dismiss.js	Persists the native dismiss click via an AJAX POST (fire-and-forget)
tests/phpunit/test-pantheon-updates.php	Gate tests: is-dismissible present, hidden when dismissed for current version, returns when newer version available
tests/phpunit/test-pantheon-update-notice-dismiss.php	Handler tests: stores available version on valid nonce, rejects bad nonce
tests/e2e/	3 BDD scenarios (renders dismissible / persists across reload / reappears on newer version); installer now also deploys the dismiss JS

Testing

Local wp-env (browser, Playwright-driven):

• Notice renders with the native dismiss X
• Click X → AJAX POST → 200 → dismissal stored in user meta
• Reload → notice stays hidden (the core AC)
• Bump available version → notice returns

Automated: phpunit (gate + handler) and BDD (dismiss / persist-across-reload / reappear) run in CI.

Test plan

• CI: all PHP legs green (phpunit)
• CI: BDD e2e green against a provisioned multidev
• Reviewer sanity-check on multisite / network admin

Open items

• Test home: the BDD harness still lives in this repo. Per Ander, it should move to the public CMS-only test framework once that lands (carried over from feat(updates): [SITE-5884] Add CSS hook and filter to hide WordPress update notice #119). Tracked separately.

References

• Jira: SITE-5883
• GitHub issue: Add option to dismiss WordPress update notice in the admin dash #116
• Predecessor: feat(updates): [SITE-5884] Add CSS hook and filter to hide WordPress update notice #119 (SITE-5884, merged)

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 8 complexity · 0 duplication

Metric	Results
Complexity	8
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}