Confirm the admin login fix is in the development release channel #64

Closed
opened 2026-06-24 22:50:03 +00:00 by mik-tf · 1 comment
Owner

The proxy change that fixes admin login on the converged stack is on the development branch, but the development release channel still serves an older build, so a fresh install would get the pre-fix proxy and login would fail. Please confirm the channel carries the current proxy build and republish it if it does not, so a clean install logs in with no manual binary swap. Part of lhumina_code/home_lhumina#313.

Signed-by: mik-tf mik-tf@noreply.invalid

The proxy change that fixes admin login on the converged stack is on the development branch, but the development release channel still serves an older build, so a fresh install would get the pre-fix proxy and login would fail. Please confirm the channel carries the current proxy build and republish it if it does not, so a clean install logs in with no manual binary swap. Part of https://forge.ourworld.tf/lhumina_code/home_lhumina/issues/313. Signed-by: mik-tf <mik-tf@noreply.invalid>
Author
Owner

Done. The development release channel now serves the current proxy build (the admin login fix), verified by a clean download whose checksum matches. One thing to flag for a separate follow up: the publish step does not replace existing files on the rolling pre-release, so a repo that already has a release keeps serving the old binaries even after a green run. Here the channel files were refreshed directly; the durable fix is to clear the old files before each publish so future pushes refresh automatically.

Signed-by: mik-tf mik-tf@noreply.invalid

Done. The development release channel now serves the current proxy build (the admin login fix), verified by a clean download whose checksum matches. One thing to flag for a separate follow up: the publish step does not replace existing files on the rolling pre-release, so a repo that already has a release keeps serving the old binaries even after a green run. Here the channel files were refreshed directly; the durable fix is to clear the old files before each publish so future pushes refresh automatically. Signed-by: mik-tf <mik-tf@noreply.invalid>
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_proxy#64
No description provided.