Release version 2.9.2

[dkotter]

This issue is for tracking the 2.9.2 release. Target release date: February 2025

Release steps

• Branch: Starting from develop, cut a release branch named release/2.9.2 for your changes
• Version bump: Bump the version number in woocommerce-gateway-gocardless.php, package.json, package-lock.json and readme.txt to 2.9.2. In woocommerce-gateway-gocardless.php update both the plugin "Version:" property and the plugin WC_GoCardless->version property
• Update @since: Find all new @since x.x.x / @since n.e.x.t lines and update those with the new version number, 2.9.2
• Changelog: Add/update the changelog in changelog.txt and readme.txt
• New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .distignore
• Readme updates: Make any other readme changes as necessary. README.md is geared toward GitHub and readme.txt contains WordPress.org-specific content. The two are slightly different
• Open PR: Open a new PR against develop from the release branch, release/2.9.2
• Run tests: On this release PR, add the labels needs: e2e testing and needs: qit default tests. This will trigger our E2E tests and the base QIT tests. Ensure these tests pass as well as all other applicable tests
• Merge: Make a non-fast-forward merge from your release branch to develop (or merge the pull request), then do the same for develop into trunk, ensuring you pull the most recent changes into develop first (git checkout develop && git pull origin develop && git checkout trunk && git pull origin trunk && git merge --no-ff develop). trunk contains the stable development version
• Push: Push your trunk branch to GitHub (e.g. git push origin trunk).
• Compare trunk to develop to ensure no additional changes were missed
• Test the pre-release ZIP locally by downloading it from the Generate ZIP file Action artifact and installing it locally. Ensure this zip has all the files we expect, that it installs and activates correctly and that all basic functionality is working
• Compare: Download the latest released zip and then run a diff compare against the generated zip, ensuring all expected changes are there (and no unexpected changes)
• Release: Create a new release, naming the tag and the release with the new version number, and targeting the trunk branch. Paste the changelog from changelog.txt into the body of the release and include a link to the closed issues on the milestone. The release should now appear under releases
• SVN: Wait for the GitHub Action to finish deploying to the WordPress.org repository
• Check WordPress.org: Ensure that the changes are live on https://wordpress.org/plugins/woocommerce-gateway-gocardless/. This may take a few minutes
• Close milestone: Edit the milestone with release date (in the Due date (optional) field) and link to GitHub release (in the Description field), then close the milestone
• Punt incomplete items: If any open issues or PRs which were milestoned for 2.9.2 do not make it into the release, update their milestone to 2.9.3 or Future Release