portal is using v5 of the upgrade client lib. it would be good to update this so we can deprecate and burninate v5 code and tests. i have a branch and can PR to portal to do this...
however there is an open question about whether portal's upgrade call is still going to be needed at all if the "group" metadata concept itself is going to go away, as that is the only real reason for portal to be involved. the working-group story is earmarked for 6.5, but I think the implications for CL apps to adopt this may be a wider CLAC discussion.
some slackery: https://carnegielearning.slack.com/archives/C055CGCRP6Z/p1779118710252079
in the meantime, seeing as that probably won't be super quick, should i go ahead and update portal so we can remove v5 endpoints in 6.5?
portal is using v5 of the upgrade client lib. it would be good to update this so we can deprecate and burninate v5 code and tests. i have a branch and can PR to portal to do this...
however there is an open question about whether portal's upgrade call is still going to be needed at all if the "group" metadata concept itself is going to go away, as that is the only real reason for portal to be involved. the working-group story is earmarked for 6.5, but I think the implications for CL apps to adopt this may be a wider CLAC discussion.
some slackery: https://carnegielearning.slack.com/archives/C055CGCRP6Z/p1779118710252079
in the meantime, seeing as that probably won't be super quick, should i go ahead and update portal so we can remove v5 endpoints in 6.5?