ref(cells): Implement org member invite redirect from old path to new#112513
Merged
ref(cells): Implement org member invite redirect from old path to new#112513
Conversation
We have to support the old invite urls for up to INVITE_DAYS_VALID (30 days) however putting this web redirect in place now allows us to clean up the rest of the frontend and api logic and other settings (such as `is_historical_monolith_region` handling) that was all connected to the legacy route.
github-actions
bot
added
the
Scope: Backend
![sentry-warden[bot]](https://avatars.githubusercontent.com/in/2755838?s=60&v=4){kind=small}
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit f77e5e9. Configure here.
Contributor
Backend Test FailuresFailures on
|
markstory
approved these changes
Apr 8, 2026
Contributor
Backend Test FailuresFailures on
|
george-sentry
pushed a commit
that referenced
this pull request
Apr 9, 2026
…#112513) We have to support the old invite urls for up to INVITE_DAYS_VALID (30 days) however putting this web redirect in place now allows us to clean up the rest of the frontend and api logic and other settings (such as `is_historical_monolith_region` handling) that was all connected to the legacy route.
lynnagara
added a commit
that referenced
this pull request
Apr 9, 2026
- removes the old /accept/:memberId/:token/ route. The component now only mounts via the org-scoped /accept/:orgId/:memberId/:token/ route - this is safe now because #112513 added a redirect that ensures the old route is never hit anymore - the react component is also simplified as it no longer has to handle the case where an org is not present
lynnagara
added a commit
that referenced
this pull request
Apr 10, 2026
- removes the old /accept/:memberId/:token/ route. The component now only mounts via the org-scoped /accept/:orgId/:memberId/:token/ route - this is safe now because #112513 added a redirect that ensures the old route is never hit anymore - the react component is also simplified as it no longer has to handle the case where an org is not present
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We have to support the old invite urls for up to INVITE_DAYS_VALID (30 days) however putting this web redirect in place now allows us to clean up the rest of the frontend and api logic and other settings (such as
is_historical_monolith_regionhandling) that was all connected to the legacy route.