Conversation
Testing every PHP minor gains little over testing the boundaries: 7.4 is the plugin's declared minimum, 8.5 is current, and 8.2 sits between as the oldest branch still receiving security support. Dropping 8.1 and 8.3 halves the matrix without losing meaningful coverage.
The captions were written for the WordPress.org readme parser, which pairs them with the SVN assets — but on GitHub that left a numbered list describing images nobody could see. Linking each caption to its copy in .wordpress-org/ makes them viewable from the repo without changing how the plugin directory renders them.
The refreshed screenshots were captured on 7.1, so the plugin has been exercised there; the header still said 6.9, which makes the directory flag the plugin as untested on current WordPress.
The 2.2.0 release listed a security fix under Fixed and 2.0.1 buried two under Maintenance, so anyone scanning the changelog for security history had to read every section. Keep a Changelog defines a Security category for exactly this; move the entries there so the 2.2.1 release notes aren't the first place the section appears.
Security release covering the ten hardening fixes from the audit, the log screen corrections, and the release automation work. Leads with an upgrade note because wp_safe_remote_get() changes behaviour for sites syndicating from hosts on private addresses.
Regenerate the POT so the catalogue's Project-Id-Version matches the release rather than 2.2.0.
Release 2.2.1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Post-release sync. The 2.2.1 release PR (#227) merged to
mainand the tag has shipped (GitHub release published, WordPress.org deployed, stable tag 2.2.1). This brings the release merge commit back intodevelopso the branch carries theVersion 2.2.1commits the next release's tooling greps for, and so the two branches don't diverge.Merge with a merge commit (not squash) to keep the release history intact.