Guidance for production users on v0.9 (Prisma/MySQL) vs. beta rewrite + account access

[GeorgBuschAdventisten]

Hi, and first of all: thanks for all the work on Snapp, and sorry to hear about the GitHub account lockout.

I run Snapp in production (currently 0.9-rc-033, Prisma + MySQL) and I'm trying to plan responsibly. I'd really appreciate some guidance:

1. Is the v0.9 (Prisma) line still maintained, or is it effectively end-of-life now that beta-version-1 is the default branch and :latest / :beta point to the rewrite?

2. Is there a documented migration path from v0.9 (Prisma + MySQL) to the beta (Drizzle + Postgres + Better-Auth)? Specifically for getting existing links/data across, does the CSV export / import preserve short codes?

3. Where should production users follow releases for now? The stable rc line appears to have stopped at 0.9-rc-033 (September 2025), the only newer Docker Hub pushes are the latest / beta rewrite images (February 2026), and GitHub commits stopped in December 2025 - so it's unclear what the canonical source of truth is during the account issue.

4. Is staying on 0.9-rc-033 the safe choice until a migration path is published?

Not asking for a timeline - just trying to understand the intended direction so I don't break a working install. Thanks again.

[archraziel88]

Thank you for the kind words and support. I plan to move codebase to this account. But been very busy at work and demotivated from the Lost account

The beta version was about to be release as not many issues came in the latest month, i wrote in the other issues/discussion a script for migrating the db but the csv should be up to the game (you may lose the metrica of course)

I plan to continue the beta into stable and limit the db to psql accepting It to be less versatile but more stable for the need of the app.

Hope you keep using snapp and to hear back from you with feedbacks about the beta version

Thank you!