Skip to content

Release to Staging - 2025-11-20#1439

Merged
transphorm merged 10 commits intostagingfrom
release/staging-2025-11-20
Nov 20, 2025
Merged

Release to Staging - 2025-11-20#1439
transphorm merged 10 commits intostagingfrom
release/staging-2025-11-20

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Nov 20, 2025

🚀 Weekly Release to Staging

Release Date: November 20, 2025
Release Branch: release/staging-2025-11-20

This automated PR promotes a snapshot of dev to staging for testing.

What's Included

All commits merged to dev up to the branch creation time.

Note: This PR uses a dedicated release branch, so new commits to dev will NOT automatically appear here.

Review Checklist

  • All CI checks pass
  • Code review completed
  • QA team notified
  • Ready to merge to staging environment

Next Steps

After merging, the staging environment will be updated. A production release PR will be created on Sunday.


This PR was automatically created by the Release Calendar workflow on November 20, 2025


Note

Cursor Bugbot is generating a summary for commit e77688b. Configure here.

seshanthS and others added 7 commits November 18, 2025 21:04
* hide unregistered documents

* redirect to 'Home' instead of 'Launch'

* RecoverWithPhraseScreen: wrap restoreAccount in try-catch

* Revert "RecoverWithPhraseScreen: wrap restoreAccount in try-catch"

This reverts commit e53b563.

* RecoverWithPhraseScreen: wrap restoreAccount in try-catch

* update lock

* fix types

* bump version

* remove launch screen

* update bundle version

* add new events

* fix nested react requires

* fix heavy tests

* address fake mocks

* fix test

* address codex and coderabbit logic conceners

* fix linting

* remove last borked react test

---------

Co-authored-by: Justin Hernandez <[email protected]>
Update build numbers and deployment timestamps after successful deployment.

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
* Prevent mobile deploy on auto-closed PRs

* Fix auto-closed PR guard in mobile deploy
* fix oom tests?

* update tests

* try fixing tests again

* fix: unblock mobile app jest runner

* fix corrupt yarn lock

* Reduce heavy React Native usage in tests (#1436)

* Reduce heavy React Native usage in tests

* Stabilize mobile tests

* prettier

* ignore podfile.lock

* fix test and gitleaks

* fix path

* update

* fix tests

* address tamagui concern
* Refactor mobile app utilities into new modules

* prettier

* update lock, feedback from codex

* fix path

* keep some files in utils

* fix tests

* update paths

* remove old docs

* cr feedback

* flatten inefficient paths

* better structure

* update test folder structure

* migrate images

* fix import

* fix Sentry path

* update ignore

* save wip migration

* more updates

* standardize component names

* rename assets

* fix linting

* add barrel exports. final refactor commit

* fix formatting

* fix nav bar

* reduce bundle size

* remove dupe license

* fix test

* fix merge issues

* add refactor doc so we can track what was imporoved

* cr feedback

* feedback
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 20, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.


Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

Bug: Useless conditional always evaluates to same value

The ternary expression const parentScreen = hasValid ? 'Home' : 'Home' always assigns 'Home' regardless of whether the user has a valid registered document. This appears to be a remnant from removing the Launch screen. The hasValid check is computed but never used, making the conditional logic ineffective. This likely breaks the intended navigation flow for users without registered documents who should be directed to onboarding.

app/src/screens/app/SplashScreen.tsx#L75-L76

const hasValid = await hasAnyValidRegisteredDocument(selfClient);
const parentScreen = hasValid ? 'Home' : 'Home';

Fix in Cursor Fix in Web


@transphorm transphorm merged commit 167dd39 into staging Nov 20, 2025
36 checks passed
@transphorm transphorm deleted the release/staging-2025-11-20 branch November 20, 2025 23:28
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.

2 participants