Update staging after creating new BUILD version in finishReleaseCycle #2906
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jag96
approved these changes
May 13, 2021
4 tasks
|
🚀 Deployed to production in version: 1.0.45-0🚀
|
14 tasks
|
🚀 Deployed to staging in version: 1.0.44-2🚀
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixing https://github.com/Expensify/Expensify/issues/157916
Following up on #2329
What happened?: After creating the new BUILD version in
finishReleaseCycle, we did not update the staging branch. Therefore, a staging deploy did not occur. That means that a newStagingDeployCashwas created, including all the deferred PRs, but that those PRs were not actually deployed. That's no bueno, so this PR fixes it.