Page MenuHomePhabricator

[keyserver] Get rid of code for updating client ThreadStore when upgrade to codeVersion 70 occurs
ClosedPublic

Authored by ashoat on Jul 15 2023, 8:03 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Jun 15, 8:03 PM
Unknown Object (File)
Fri, Jun 14, 3:25 AM
Unknown Object (File)
Thu, Jun 13, 8:13 AM
Unknown Object (File)
Thu, Jun 13, 6:36 AM
Unknown Object (File)
Mon, Jun 3, 11:36 PM
Unknown Object (File)
Mon, Jun 3, 11:36 PM
Unknown Object (File)
Mon, Jun 3, 10:14 PM
Unknown Object (File)
May 26 2024, 11:47 PM
Subscribers

Details

Summary

See the first diff in the stack. We're no longer expecting to see such an old codeVersion, so I'm going to delete this code.

This is admittedly slightly more risky than some of the other diffs in the stack, because this doesn't just break the USE of such an old codeVersion, but rather breaks the upgrade FROM such an old codeVersion.

However, I think it's safe because we don't currently have any logged-in sessions with such an old codeVersion, and we prevent log in / registration with such an old codeVersion in the parent diff. So we don't expect such an upgrade to occur.

Depends on D8503

Test Plan

I tested this whole stack together by playing around with the web app and making sure thread mutation endpoints seemed to work correctly

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable