fix: remove legacy register compatibility flow - #5921
Merged
Conversation
Contributor
🦋 Changeset detectedLatest commit: 5ffe0f5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
alx-xo
changed the title
alx-xo
force-pushed
the
GRW-20-remove-register
branch
from
September 3, 2026 01:07
79abf46 to
5ffe0f5
Compare
Collaborator
🚀 Preview Environment (PR #5921)Preview URL: https://pr-5921.dev.getgram.ai
Gram Preview Bot |
alx-xo
added
the
review:bypass
![gram-bot[bot]](https://avatars.githubusercontent.com/in/1956617?s=60&v=4){kind=small}
Contributor
Author
|
Merging this as there have been no views on the /register route in the past 7 days, last view was Aug 23 
|
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
GRW-20
Summary
Remove the legacy
/registercompatibility flow now that signup and zero-organization onboarding are handled by the session-aware/sign-upflow. This deletes the standaloneRegistercomponent and the tests for its obsolete session, organization, assistants-disposition, and destination-routing branches.The supported onboarding paths remain unchanged: logged-out signup and authenticated zero-organization onboarding use
/sign-up, existing users use/login, and CLI onboarding sends zero-organization sessions to/sign-upwith its callback destination. Slack registration, the registration API, and OAuth dynamic client registration are separate flows and are not affected.The old path remains only as a minimal route-table redirect to
/sign-upso stale links do not fail. It carries none of the removed compatibility behavior.Motivation
The session-aware signup flow has replaced
/register, and production traffic no longer depends on the legacy routing behavior. Removing it eliminates redundant onboarding logic and its dedicated test surface.