Automation Scripts for Releasing Gutenberg-Mobile Updates to the WordPress Mobile Apps.
The preferred automation flow now uses the gbm-cli tool. See the tool README for more information. Follow the Installing section to get started.
There are no prerequisites to using the gbm-cli tool beyond what is used to develop on Gutenberg Mobile.
It does use the same Github authentication as gh so it is recommended to run gh auth before using the tool. See Authentication for alternatives.
nvm is the recommended node manager for running the gbm-cli release commands.
When preparing Gutenberg for a release it is possible to set the global node version to the current version required by Gutenberg.
At the moment this is not possible when preparing a Gutenberg Mobile PR locally since there are multiple node versions during the preparation.
To be able to run the legacy automation script make sure you have installed:
brew install ghbrew install jqRun the script: ./release_automation.sh
You can test the scripts on forked repos. Please follow the instructions on top of the release_automation.sh file.
Occasionally, the script may encounter an error while running. Because the project makes use of a node_modules directory within the Gutenberg submodule, it may be useful in some cases to manually install npm dependencies there. By default, running npm install (or npm i) from within the gutenberg-mobile directory will trigger npm ci to run within the gutenberg directory, but sometimes it may also be helpful to try:
cd ./gutenberg
npm iIt can also be useful to run cd ./gutenberg && npm run distclean