Create a v2 (and v1?) docker tag #800

Closed
opened 2026-02-04 21:22:27 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @deviantintegral on GitHub (Sep 1, 2025).

Is this a feature for the backend or frontend?

Backend

What would you like?

Currently latest points to a v1 release, while the docs point new users to the 2.0 RC's.

I would like to be able to point Planka to a v2 (or 2, or whatever) tag representing the major version that automatically tracks security and patch releases. That way, I can set my server to automatically re-pull new 2.0 releases without having to hunt down new version numbers.

Why is this needed?

Automatic updates (combined with good backups and rollback strategies!) are great for homelabs and smaller installs where the cost of being behind a security fix is greater than the chance of an upgrade breaking things.

Other information

latest is close to this, but has the issue of breaking v1 users if they pull and unexpectedly get to v2. If v1 is going to be supported for any length of time, it may be good to add a corresponding 1 or v1 tag for those users to switch to.

Originally created by @deviantintegral on GitHub (Sep 1, 2025). ### Is this a feature for the backend or frontend? Backend ### What would you like? Currently `latest` points to a v1 release, while the docs point new users to the 2.0 RC's. I would like to be able to point Planka to a v2 (or 2, or whatever) tag representing the major version that automatically tracks security and patch releases. That way, I can set my server to automatically re-pull new 2.0 releases without having to hunt down new version numbers. ### Why is this needed? Automatic updates (combined with good backups and rollback strategies!) are great for homelabs and smaller installs where the cost of being behind a security fix is greater than the chance of an upgrade breaking things. ### Other information `latest` is close to this, but has the issue of breaking v1 users if they pull and unexpectedly get to v2. If v1 is going to be supported for any length of time, it may be good to add a corresponding `1` or `v1` tag for those users to switch to.
Author
Owner

@meltyshev commented on GitHub (Sep 2, 2025):

Hey! We're not setting it to latest right now because it's still in RC status. But we're aiming to release the final v2 very soon, and of course we'll tag it as latest then :)

@meltyshev commented on GitHub (Sep 2, 2025): Hey! We're not setting it to `latest` right now because it's still in RC status. But we're aiming to release the final v2 very soon, and of course we'll tag it as `latest` then :)
Author
Owner

@deviantintegral commented on GitHub (Sep 3, 2025):

Will that cause issues for users currently using latest, given there are manual upgrade steps to follow?

@deviantintegral commented on GitHub (Sep 3, 2025): Will that cause issues for users currently using latest, given there are manual upgrade steps to follow?
Author
Owner

@meltyshev commented on GitHub (Sep 4, 2025):

Will that cause issues for users currently using latest, given there are manual upgrade steps to follow?

Nope, there should be no issues upgrading. If you're on v1, you'll need to go through ~11 manual steps as described here: https://docs.planka.cloud/docs/upgrade-to-v2/docker/ - everything else (database and images) will be upgraded automatically. And if you're updating from the current RC version, it will just update automatically.

@meltyshev commented on GitHub (Sep 4, 2025): > Will that cause issues for users currently using latest, given there are manual upgrade steps to follow? Nope, there should be no issues upgrading. If you're on v1, you'll need to go through ~11 manual steps as described here: https://docs.planka.cloud/docs/upgrade-to-v2/docker/ - everything else (database and images) will be upgraded automatically. And if you're updating from the current RC version, it will just update automatically.
Author
Owner

@deviantintegral commented on GitHub (Sep 4, 2025):

Sounds good, thanks!

@deviantintegral commented on GitHub (Sep 4, 2025): Sounds good, thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#800