Current release status?

[edenworky]

I spent some time debugging why the 1time-web image isn't reading BACKEND_UPSTREAM when I saw the last release was 2 months and 69 commits ago. Having resolved that I also saw there's no file upload in the web UI.

What's the current timeline for the next release? Is master stable enough to build off of? The file sharing functionality is crucial for me. Is there anything blocking the release, or is it ready to cut? Anything I can help with?

Tysm, this is very lovely

[shingrus]

Hi!
The release was sitting there as a draft. Published
now: https://github.com/shingrus/1time.io/releases/tag/v0.10.0

Good news is the images were never behind. The build fires on the tag, not on
the release, so v0.10.0 and latest have been on GHCR since Sep 14. Pull
latest and you're current.

File upload has been in the web UI since v0.4 though - it's at
/secure-file-sharing/, there's a "One-time file" link in the switcher on the
homepage. It's in 0.9 too.
If the page loads but the upload dies, that's
probably just your /api/ proxy, same thing you were chasing.

Speaking of which, what actually went wrong with BACKEND_UPSTREAM? It's been
plumbed through since 0.7 and I can't see the hole. If you've got the logs I'd
like to fix it properly.

Build off v0.10.0 rather than master, but master is fine too.

[edenworky]

Hey, first of all tysm!

I see the release in time.io/releases, and I'm not sure why that's not enough for the package registry to update (never used github's registries) but if you look at the 1time-web package and the 1time-backend package you'll see these were last synced up 6 months ago which as you say is way behind the actual recent releases

And yeah I see the file sharing stuff on the public version! That's why I was so surprised when they weren't in the self-hosted one haha (btw, the new colors are much nicer)

[shingrus]

omg, it was my fault.

I renamed this repo from 1time to 1time.io in March. The workflow built the
image name from the repo slug, so it started pushing to 1time.io-web while the
compose file kept pointing at 1time-web — a package untouched since
2026-03-21. You've been running a six-month-old image. File sharing landed in
v0.4, BACKEND_UPSTREAM in v0.7.0; neither was in there. Nothing for you to
debug.

Fixed on master, publishing to both names now. Once it runs, docker compose pull is all you need.

Meanwhile: ghcr.io/shingrus/1time.io-web:v0.10.0 + -backend:v0.10.0.

Thanks for being stubborn about this one.