[No QA]Tag the `staging` branch instead of `main` for pre-release #47253

AndrewGable · 2024-08-12T17:52:35Z

Details

Correctly tag the staging branch instead of the main branch while we are CP-ing and additionally fix HybridApp deploys.

Fixed Issues

Fixes CP process

Tests

CP this PR and verify it tags the staging branch correctly

QA Steps

N/A

PR Author Checklist

I linked the correct issue in the ### Fixed Issues section above
I wrote clear testing steps that cover the changes made in this PR
- I added steps for local testing in the Tests section
- I added steps for the expected offline behavior in the Offline steps section
- I added steps for Staging and/or Production testing in the QA steps section
- I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
- I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
I included screenshots or videos for tests on all platforms
I ran the tests on all platforms & verified they passed on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
I followed proper code patterns (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  - If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I followed the guidelines as stated in the Review Guidelines
I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
I verified that if a function's arguments changed that all usages have also been updated correctly
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

melvin-bot · 2024-08-12T17:52:39Z

@ Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

AndrewGable · 2024-08-12T18:29:47Z

.github/workflows/platformDeploy.yml

      - name: Upload Android build to Browser Stack
        if: ${{ !fromJSON(env.SHOULD_DEPLOY_PRODUCTION) }}
        run: curl -u "$BROWSERSTACK" -X POST "https://api-cloud.browserstack.com/app-live/upload" -F "file=@./android/app/build/outputs/bundle/productionRelease/app-production-release.aab"
        env:
          BROWSERSTACK: ${{ secrets.BROWSERSTACK }}

+      - name: Upload Android sourcemaps to GitHub Release
+        if: ${{ !fromJSON(env.SHOULD_DEPLOY_PRODUCTION) }}


@roryabraham We should only upload Android/iOS on staging, right?

AndrewGable · 2024-08-12T18:30:21Z

.github/workflows/platformDeploy.yml

-          name: web-build
-          path: dist
+      - name: Upload web sourcemaps to GitHub Release
+        run: gh release upload ${{ github.event.release.tag_name }} dist/merged-source-map.js.map#web-sourcemap-${{ github.event.release.tag_name }} --clobber


@roryabraham We should always upload web on staging and production, right? Then use the --clobber flag to update the file?

this works, but it just means that when a staging version becomes a production version, the artifacts for the staging version with the same tag are deleted. I think that's fine though

roryabraham · 2024-08-12T19:53:24Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

[No QA]Tag the `staging` branch instead of `main` for pre-release (cherry picked from commit 8ddece2) (CP triggered by AndrewGable)

OSBotify · 2024-08-12T20:10:13Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2024-08-12T20:37:33Z

🚀 Cherry-picked to staging by https://github.com/AndrewGable in version: 9.0.19-4 🚀

platform	result
🤖 android 🤖	failure ❌
🖥 desktop 🖥	failure ❌
🍎 iOS 🍎	failure ❌
🕸 web 🕸	failure ❌

OSBotify · 2024-08-12T22:09:36Z

🚀 Cherry-picked to staging by https://github.com/AndrewGable in version: 9.0.19-5 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅

Beamanator · 2024-08-14T20:57:22Z

FYI I believe this was deployed to prod yesterday, from this checklist - #47219

AndrewGable added 2 commits August 12, 2024 11:49

Tag the staging branch instead of main for pre-release

ed188fa

Deploy HybridApp on a pre-release

88fa4e6

AndrewGable requested a review from roryabraham August 12, 2024 17:52

AndrewGable self-assigned this Aug 12, 2024

AndrewGable requested a review from a team as a code owner August 12, 2024 17:52

melvin-bot bot removed the request for review from a team August 12, 2024 17:52

AndrewGable added 2 commits August 12, 2024 11:53

Use correct flag 🙈

a3802f4

Update to upload all assets to releases instead of build artifacts

0c080cd

AndrewGable commented Aug 12, 2024

View reviewed changes

roryabraham approved these changes Aug 12, 2024

View reviewed changes

roryabraham merged commit 8ddece2 into main Aug 12, 2024
8 of 11 checks passed

roryabraham deleted the andrew-staging-release branch August 12, 2024 19:53

OSBotify pushed a commit that referenced this pull request Aug 12, 2024

Merge pull request #47253 from Expensify/andrew-staging-release

9505a93

[No QA]Tag the `staging` branch instead of `main` for pre-release (cherry picked from commit 8ddece2) (CP triggered by AndrewGable)

github-actions bot added the CP Staging marks PRs that have been CP'd to staging label Aug 12, 2024

github-actions bot mentioned this pull request Aug 12, 2024

Deploy Checklist: New Expensify 2024-08-12 #47219

Closed

90 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[No QA]Tag the `staging` branch instead of `main` for pre-release #47253

[No QA]Tag the `staging` branch instead of `main` for pre-release #47253

AndrewGable commented Aug 12, 2024

melvin-bot bot commented Aug 12, 2024

AndrewGable Aug 12, 2024

roryabraham Aug 12, 2024

AndrewGable Aug 12, 2024

roryabraham Aug 12, 2024

roryabraham commented Aug 12, 2024

OSBotify commented Aug 12, 2024

OSBotify commented Aug 12, 2024

OSBotify commented Aug 12, 2024

Beamanator commented Aug 14, 2024

[No QA]Tag the staging branch instead of main for pre-release #47253

[No QA]Tag the staging branch instead of main for pre-release #47253

Conversation

AndrewGable commented Aug 12, 2024

Details

Fixed Issues

Tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Aug 12, 2024

AndrewGable Aug 12, 2024

Choose a reason for hiding this comment

roryabraham Aug 12, 2024

Choose a reason for hiding this comment

AndrewGable Aug 12, 2024

Choose a reason for hiding this comment

roryabraham Aug 12, 2024

Choose a reason for hiding this comment

roryabraham commented Aug 12, 2024

Reviewer Checklist

Screenshots/Videos

OSBotify commented Aug 12, 2024

OSBotify commented Aug 12, 2024

OSBotify commented Aug 12, 2024

Beamanator commented Aug 14, 2024

[No QA]Tag the `staging` branch instead of `main` for pre-release #47253

[No QA]Tag the `staging` branch instead of `main` for pre-release #47253