-
Notifications
You must be signed in to change notification settings - Fork 42
Deploying new versions
Nabeel Molham edited this page Aug 21, 2024
·
9 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
version number. There is no need to runcomposer update
to update thecomposer.lock
file because the package version is not include in that file. - Bump the
package.json
version number usingnpm version --no-git-tag-version --allow-same-version {version}
. This will update the version number in thepackage.json
andpackage-lock.json
files without updating any of the dependencies. - 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
npm run build
to compile assets and generate an updated POT file - Run the test suites and confirm they are passing
./vendor/bin/phpunit
codecept run integration
codecept run acceptance
- Commit with a message of
Version {version number}
- Wait until all the checks have passed like the ones executed by Travis CI
- 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
- Update the Upgrade-guide
-
Could not find an option named "sourcemap"
- Install Ruby
- Run
gem install sass
-
parcel: not found
- Install parcel
-
.../wc-plugin-framework/woocommerce/payment-gateway/assets/js/frontend/sv-wc-payment-gateway-google-pay.js: Invalid Version: undefined
- Open the
.js
file - Add the following snippet to the top of the file
/** * Version 5.10.5 */
- Run the
npx run build
again - Rollback the changes to the
.js
file
- Open the
- Home
- General Usage
- Payment Gateways
- WooCommerce Blocks
- Updating
- Testing
- Workflow