-
Notifications
You must be signed in to change notification settings - Fork 15
Milestone
Description
This issue is for tracking the 1.6.10 release. Target release date: January 13 2025
Pre-release steps
- Merge Bump WooCommerce "tested up to" version 9.5 #269
- Merge Move to
@woocommerce/e2e-utils-playwright
#270 - Merge Compatibility testing with WC 9.6 #275
Release steps
- Branch: Starting from
trunk
, cut a release branch namedrelease/1.6.10
- Version bump: Bump the version number in
woocommerce-gateway-payfast.php
,package.json
,package-lock.json
andreadme.txt
to 1.6.10. Inwoocommerce-gateway-payfast.php
update both the plugin "Version:" property and the pluginWC_GATEWAY_PAYFAST_VERSION
constant - Update
@since
: Find all new@since x.x.x
/@since n.e.x.t
lines and update those with the new version number, 1.6.10 - Generate changelog: Locally, generate the changelog by running the following Woorelease command:
php woorelease.phar cl:generate --product_version=1.6.10 https://github.com/woocommerce/woocommerce-gateway-payfast/tree/trunk
. Ensure the changelog updates look correct - Update changelog: Take the changelog generated from the previous step and update the release PR with those changes, both in the
changelog.txt
file andreadme.txt
file - Open PR: Open a new PR against
trunk
from the release branch,release/1.6.10
- Run tests: On this release PR, add the label
needs: qit default tests
andneeds: e2e testing
. This will trigger the default QIT tests (activation, API and E2E) and our E2E tests. Ensure these tests pass as well as all other applicable tests - Merge: Merge the release PR into
trunk
- Prepare ZIP: Prepare the zip by running Woorelease locally on the
trunk
branch:php woorelease.phar build https://github.com/woocommerce/woocommerce-gateway-payfast/tree/trunk
. Make sure you are running the proper versions ofnode
,npm
andcomposer
to ensure the built files are consistent across releases. Versions can be found inpackage.json
- 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)
- Test ZIP: Take the ZIP generated from the previous step and test this locally, ensuring version numbers look correct, the changelog looks correct and the plugin installs and activates properly
- Attach ZIP: Attach the ZIP to this issue and ping the Automattic team in the
#a8c-10up-woo-support
channel to complete the release