Skip to content

Deploy Checklist: New Expensify 2024-02-13 #36429

Closed

Description

@github-actions

Release Version: 1.4.41-12
Compare Changes: production...staging

This release contains changes from the following pull requests:

Deploy Blockers:

Deployer verifications:

  • I checked the App Timing Dashboard and verified this release does not cause a noticeable performance regression.
  • I checked Firebase Crashlytics and verified that this release does not introduce any new crashes. More detailed instructions on this verification can be found here.
  • I checked GitHub Status and verified there is no reported incident with Actions.

cc @Expensify/applauseleads

Activity

  1. blimpich commented on Feb 13, 2024

    @blimpich
    Contributor

    Demoting 36434

  2. amyevans commented on Feb 13, 2024

    @amyevans
    Contributor

    Demoted #36437

  3. OSBotify commented on Feb 14, 2024

    @OSBotify
    Contributor

    🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.4.41-0 🚀

  4. Beamanator commented on Feb 14, 2024

    @Beamanator
    Contributor

    Marked #36456 as NAB b/c we consider it a pretty strange edge case

  5. Beamanator commented on Feb 14, 2024

    @Beamanator
    Contributor

    Also marked #36455 as NAB, it's not really broken - and it's a test that we'll be updating over the next few weeks

  6. Beamanator commented on Feb 14, 2024

    @Beamanator
    Contributor

    #36458 also got marked nab as it's quite a small design bug that will be quick to fix

  7. kavimuru commented on Feb 14, 2024

    @kavimuru

    Regression is 4% left.
    #31055 failing with #36455
    #34752 failing with #36479
    #34498 failing with #36449, #36451, #36447 and blocked in desktop with KI #36368
    #34303 failing with #36433 on desktop
    We still have validation pending on other unchecked PRs

  8. Julesssss commented on Feb 14, 2024

    @Julesssss
    Contributor

    Checking off #36502 as it's not a big problem. Will fix without it being a blocker

  9. dangrous commented on Feb 14, 2024

    @dangrous
    Contributor

    #36487 is not a blocker and is sort of a dupe of #36455. Checking off.

  10. kavimuru commented on Feb 14, 2024

    @kavimuru

    Regression completed.

    Unchecked PRs:
    #31055 failing with #36455
    #34752 failing with #36479
    #34498 failing with #36449,#36451,#36447 and blocked in desktop with KI36368
    #34303 failing with #36433 on desktop
    #34963 blocked by #36479
    #35287 blocked by #36433
    #35841 failing with #36434 but closed as not reproduced, checking it off
    #35853 blocked by #36433
    #36204 blocked by #36433 in iOS (tester does not have an account with previous requests to validate the PR. Because PR steps does not require a new IOU)
    #35645 - Looks internal testing, can I check it off?

    Open Blockers:
    #36433
    #36346
    #36438
    #36454
    #36457
    #36479
    #36481
    #36483
    #36490
    #36510
    #36517

    We are validating the 2 cps now.

  11. rlinoz commented on Feb 14, 2024

    @rlinoz
    Contributor

    Checking off #36510 as this is already in prod.

  12. amyevans commented on Feb 14, 2024

    @amyevans
    Contributor

    Checked off #36454 following CP/retest

  13. mountiny commented on Feb 14, 2024

    @mountiny
    Contributor

    checking #36479 off, its backend blocker

  14. AndrewGable commented on Feb 15, 2024

    @AndrewGable
    Contributor
  15. thienlnam commented on Feb 15, 2024

    @thienlnam
    Contributor

    Only fresh crash is for
    ImageMetaData.getColorSpace - which only happened for 1 user on 1.4.38-6 so it seems fine to ignore

  16. thienlnam commented on Feb 15, 2024

    @thienlnam
    Contributor

    Kicking off the deploy so we can get this fireroom fix to prod

  17. thienlnam commented on Feb 15, 2024

    @thienlnam
    Contributor

    :shipit:

  18. os-botify commented on Feb 15, 2024

    @os-botify

    This issue either has unchecked items or has not yet been marked with the :shipit: emoji of approval.
    Reopening!

  19. melvin-bot commented on Feb 15, 2024

    @melvin-bot

    📣 @os-botify[bot]! 📣
    Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
    Please follow these steps:

    1. Make sure you've read and understood the contributing guidelines.
    2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
    3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
    4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
      Screen Shot 2022-11-16 at 4 42 54 PM
      Format:
    Contributor details
    Your Expensify account email: <REPLACE EMAIL HERE>
    Upwork Profile Link: <REPLACE LINK HERE>
    
  20. thienlnam commented on Feb 15, 2024

    @thienlnam
    Contributor

    :shipit:

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions