Release process

Scenario: Current develop branch is at 7.1.7-dev and we want to release it as 7.1.7

• rm -Rf vendor && rm composer.lock && composer install && composer run-script test
• commit -m "update dependencies"
• git push
• ensure CHANGELOG.md contains all the relevant changes since the previous release
• commit + push any changes to CHANGELOG.md
• git checkout master
• git reset --hard develop
• edit wp2static.php, removing the -dev from the version number references.
• git commit -m "release 7.1.7
• git tag 7.1.7
• git push && git push --tag
• create a GitHub release, using the same tag, ie 7.1.7
• copy the same format as previous release. Include the same changes from CHANGELOG.md
• confirm repo homepage shows latest release
• confirm Packagist shows latest release
• composer run-script build wp2static-7.1.7
• md5 wp2static-7.1.7.zip > wp2static-7.1.7.zip.md5
• upload zip and MD5 to S3 bucket
• update bundle in Snipcart
• update zip and MD5 on thanks-for-supporting page in wp2static-www
• update bundle Snipcart product attributes in wp2static-www
• deploy latest wp2static-www
• git checkout develop
• edit ./wp2static.php, bumping version number to development version of next planned release version (minor point release if unsure)
• in this scenario, we'll bump it to 7.1.8-dev
• add a 7.1.8 section to CHANGELOG.md
• git commit -m "reset dev version after release
• git push

Post-release process

(This would preferably be done pre-release, but may be deferred when we want to push out a new WP2Static core verison quickly)

Run the Lokl script to pull and build latest from WP2Static core and add-on sources. Build new base image and ensure that core and all addons activate without error. Smoke test simple deployment to ZIP/Netlify and ensure homepage and subpages are loading fine.