Clean up the check aztec step in the release checklist
jhnstn opened this issue · comments
The current task shows:
Verify that gutenberg-mobile/RNTAztecView.podspec and gutenberg-mobile/gutenberg/packages/react-native-aztec/RNTAztecView.podspec refer to the same WordPress-Aztec-iOS version and are pointing to a stable, tagged release (e.g. 1.14.1). If they are not, we may need to [create a new Aztec](https://jhnstnp2.wordpress.com/?draft=1041#create-a-new-aztec-release) release.
The anchor link might not be present if running the checklist generator with the --a flag. Instead it should point to a section in the release documentation regarding updating Aztec
The current release script does verify Aztec so I'm wondering if we need this step at all. Once we have the "Update Aztec" documentation up we could have the current release script point there if it encounters a non production version of Aztec in the configs.
This same behavior can be included in the new CLI release scripts.