Skip to content

[Home Page] Remove Beta Gate for Release 1 #80139

Closed

Description

@grgia

Remove all beta gates used in Release 1.

This will release the feature to all users and allow us to use the same beta for Release 2.

Activity

  1. self-assigned this
    on Jan 21, 2026
  2. moved this from Backlog to Ready in Home pageon Jan 28, 2026
  3. melvin-bot commented on Jan 30, 2026

    @melvin-bot

    @mountiny, @grgia Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  4. moved this from Ready to In progress in Home pageon Jan 30, 2026
  5. melvin-bot commented on Jan 31, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  6. melvin-bot commented on Jan 31, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  7. melvin-bot commented on Feb 2, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  8. melvin-bot commented on Feb 3, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  9. melvin-bot commented on Feb 3, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  10. melvin-bot commented on Feb 5, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  11. moved this from In progress to Done in Home pageon Feb 6, 2026
  12. nyomanjyotisa commented on Jul 13, 2026

    @nyomanjyotisa
    Member

    The implementation for this issue in #80965 changed the logged-out SignInPage route to the root-level SCREENS.HOME. Because that route had no top-level path mapping, React Navigation serialized the raw route name as /Home, introducing #94450. #94433 fixed it by registering SignInPage under TAB_NAVIGATOR, which has no path of its own and keeps the logged-out URL at /.

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

Metadata

Metadata

Labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions