performwp / performwp/perform

WordPress 7.1 compatibility validation and Tested up to update

Open
#243 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
5
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Goal

Validate Perform against WordPress 7.1 before the scheduled 19 August 2026 release, then update the stable-tag readme only after compatibility evidence is complete.

Required work

  • Test the packaged plugin on the latest WordPress 7.1 release candidate (and the supported PHP/browser matrix used by this repository).
  • Run Plugin Check against the packaged plugin and record actionable findings.
  • Review the applicable WordPress 7.1 changes: iframed post editor, client-side media processing, @wordpress/components changes, persistent editor toolbar, SVG Icon API, jQuery UI 1.14.2, and Abilities API changes. Mark non-applicable surfaces explicitly with evidence.
  • Focus for this plugin: performance/admin dashboards, editor-facing assets, media processing hooks, and any Abilities API integration.
  • Fix compatibility blockers in this release train; keep unrelated feature work out of scope.
  • After proof passes, update the stable-tag readme.txt line to Tested up to: 7.1, refresh the changelog/release notes, and verify the packaged artifact contains the updated metadata.

Acceptance criteria

  • WordPress 7.1 RC test site and relevant editor/admin workflows pass without new regressions.
  • Plugin Check output is attached, with no unresolved release-blocking finding.
  • Automated tests, lint/static checks, and package validation pass.
  • The stable-tag readme update is made only after the above evidence exists.
  • This issue is included in the milestone containing it and called out in the next minor release notes.

References

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the packaged plugin on a WordPress 7.1 release-candidate test site, covering the supported PHP/browser matrix and the listed editor, media, admin, and Abilities API surfaces. Run Plugin Check and the repository's automated tests, lint, static checks, and package validation; record evidence for applicable and non-applicable changes. Done means release blockers are resolved, the artifact is verified, and stable-tag readme.txt and release notes are updated only after the checks pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
documentation, performance, release, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.