-
Notifications
You must be signed in to change notification settings - Fork 42
Deploying new versions
Adriano Castro edited this page Oct 14, 2020
·
11 revisions
The following outlines the process for deploying new versions of this framework. After merging the relevant PRs:
- Bump all versioned namespaces to the new plugin version number, i.e.
v5_5_4
- Be sure to also bump those found in
/tests
- Do a search and ensure no instances of the previous namespace are present
- Do a search for
x.y.z
and replace them for the new version number
- Be sure to also bump those found in
- Bump the
SV_WC_Plugin::VERSION
constant to the new version - Bump the
composer.json
andpackage.json
version numbers - Bump the
SV_WC_Framework_Plugin_Loader::FRAMEWORK_VERSION
constant. This is only used by implementing plugins, but it's good to keep it up to date - Update
/woocommerce/changelog.txt
with the final date and version - Run
grunt
to compile assets and generate an updated POT file - Run the test suites and confirm they are passing
codecept run unit
codecept run integration
codecept run acceptance
- Commit with a message of
Version {version number}
- Confirm that the automated tests pass ✅
- Copy the bullet points of the version's changelog entry
- Create a new release
- Name the tag the plain version number (no
v
or other prefix) - Name the release with the
v
prefix - Paste in the changelog entries as the description
- Name the tag the plain version number (no
- Home
- General Usage
- Payment Gateways
- WooCommerce Blocks
- Updating
- Testing
- Workflow