Release version 2.0.20 - #1080
Merged
Merged
Conversation
Composer: * No need for requiring the Composer PHPCS plugin anymore as it now comes automatically with WPCS and removing the requirement allows WPCS to manage the supported versions, preventing conflicts (and will update us to the 1.0.0 version). * As the minimum supported version of PHPCS for WPCS is now above 3.7.1, we don't need the explicit require for PHPCS anymore either. PHPCS ruleset: * Various tweaks to the sniff and property names as per the changes in WPCS 3.0.0. Refs: * https://github.com/WordPress/WordPress-Coding-Standards/releases/tag/3.0.0 * https://github.com/WordPress/WordPress-Coding-Standards/wiki/Upgrade-Guide-to-WordPressCS-3.0.0-for-ruleset-maintainers
... for a parameter using a reserved keyword for its name, which is discouraged. This method is deprecated, so changing this is irrelevant.
... and make the build up of the `$request` explicit. This removes a warning about a (not) "unused parameter".
... as WordPressCS will not throw deprecations anymore.
Each of these dependencies has a minimum PHP version which aligns with the minimum PHP version of this package, so these can safely be "bumped" to enforce using the latest versions of these dependencies (which is what would be used in CI anyway).
Setup-PHP will normally "gracefully" show a warning and not fail the build when an extension or tool failed to install. In most cases, this is not particularly useful as that means that either there will be a failure later on in the build due to the extension or tool missing, or the build will not be representative of what is supposed to be tested. This commit changes this behaviour to fail select builds at the `setup-php` step, which also makes debugging these type of build failures much more straight-forward. Ref: https://github.com/shivammathur/setup-php?tab=readme-ov-file#fail-fast-optional
* Tighten up the GitHub Actions workflow permissions. * Add inline docs to the permissions directives.
The test requests an HTTPS host and expects a 200, which only demonstrates anything if that host serves a different certificate when no SNI is sent. It no longer does, so a transport which quietly stopped sending SNI would still pass. The host has meanwhile also started answering 403 to every client, including a plain `curl`, so the test fails for reasons entirely unrelated to the library. Pointing it at another host would get the suite green again, but it would also leave a test standing which looks like it covers something it does not. Skipping it says what is actually the case, and keeps the intent visible for whoever picks it up. Refs #1077, which has the measurements and the options for getting real coverage back.
Bumps the action-runners group with 1 update in the / directory: [ruby/setup-ruby](https://github.com/ruby/setup-ruby). Updates `ruby/setup-ruby` from 1.319.0 to 1.321.0 - [Release notes](https://github.com/ruby/setup-ruby/releases) - [Changelog](https://github.com/ruby/setup-ruby/blob/master/release.rb) - [Commits](ruby/setup-ruby@003a5c4...95ef2b0) --- updated-dependencies: - dependency-name: ruby/setup-ruby dependency-version: 1.321.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: action-runners ... Signed-off-by: dependabot[bot] <support@github.com>
* Includes updating the version number constant.
schlessera
approved these changes
Aug 31, 2026
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
3 participants
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.
Detailed Description
The only thing new here is the changelog commit, everything else is cherrypicked from previously approved PRs.
Closes #1068
Release checklist
release/vx.x.xbranch.developto the release branch, including commits related to CI updates.src/Requests.php- PR Release version 2.0.20 #1080.** In case of a short-lived release branch, add the changelog as the last commit to the release branch and pull the release branch.
stableand push the tag.develop!) & copy & paste the changelog to it.Make sure to copy the links to the issues and the links to the GH usernames from the bottom of the changelog!
Note: it is important to do this after the release as otherwise the information about the latest release
in the site will not be updated correctly from the GitHub API.
stableinto thedevelopbranch.