Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 1.32.0 #2467

Merged
merged 104 commits into from
Jul 10, 2020
Merged

Release 1.32.0 #2467

merged 104 commits into from
Jul 10, 2020

Conversation

SergioEstevao
Copy link
Contributor

@SergioEstevao SergioEstevao commented Jul 8, 2020

Release for Gutenberg Mobile 1.32.0

Related PRs

Extra PRs that Landed After the Release Was Cut

NA

Changes

Test plan

  • Use the main WP apps to test the changes above.
  • Check WPAndroid and WPiOS PRs if there are specific tests to run.
  • Smoke test the main WP apps for general writing flow.

Release Submission Checklist

  • Release number was bumped
  • Aztec dependencies are pointing to a stable release
    • iOS: 'grep WordPressAztec-iOS RNTAztecView.podspec'
    • Android: 'grep aztecVersion react-native-aztec/android/build.gradle'
  • Gutenberg 'Podfile' and 'Podfile.lock' inside './ios/' are updated to the release number
  • Bundle package of the release is updated
  • Check if RELEASE-NOTES.txt is updated with all the changes that made it to the release

SergioEstevao and others added 30 commits June 17, 2020 17:03
…1.0_to_develop

Release/merge main 1.31.0 to develop
…ress

# Conflicts:
#	bundle/android/App.js
#	bundle/android/App.js.map
#	bundle/ios/App.js
#	bundle/ios/App.js.map
#	gutenberg
@peril-wordpress-mobile
Copy link

peril-wordpress-mobile bot commented Jul 8, 2020

Wanna run full suite of Android and iOS UI tests? Click here and 'Approve' CI job!

@SergioEstevao SergioEstevao requested a review from mchowning July 8, 2020 12:53
@SergioEstevao SergioEstevao added this to the 1.32 milestone Jul 8, 2020
@SergioEstevao SergioEstevao marked this pull request as ready for review July 8, 2020 12:53
Copy link
Contributor

@mchowning mchowning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested and everything looks good! :shipit:

@SergioEstevao SergioEstevao merged commit d6c6172 into main Jul 10, 2020
@SergioEstevao SergioEstevao deleted the release/1.32.0 branch July 10, 2020 21:01
@hypest
Copy link
Contributor

hypest commented Jul 14, 2020

👋 looks like we didn't update the package-lock.json and the version mentioned there is still the previous (1.31.1) one. It's not easy to manually merge package-lock.json conflicts so, may I suggest adding a step to the release process to ensure that the lock file has the proper version?

Without updating the lock file, npm install ends up introducing changes to it.

@mchowning
Copy link
Contributor

looks like we didn't update the package-lock.json and the version mentioned there is still the previous (1.31.1) one. It's not easy to manually merge package-lock.json conflicts so, may I suggest adding a step to the release process to ensure that the lock file has the proper version?

This is addressed in #2490.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.