starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Enhancement]: major version docker image tag #3175

New Issue
Open
opened 2026-04-25 00:14:06 +02:00 by adam · 2 comments
adam commented 2026-04-25 00:14:06 +02:00
Owner
Copy Link
Copy Source

Originally created by @Sjoerd82 on GitHub (Jan 5, 2026).

Type of Enhancement

None

Describe the Feature/Enhancement

Currently we have the "edge", "latest" and explicit version "2.32.1", etc. tags. Is it possible to add a "2" tag for the latest version 2 major version. Currently set to "latest" but afraid I will accidentaly upgrade to a version that has breaking changes.

Why would this be helpful?

This way I can add this major version to my Docker Compose file, and automatically update by restarting, knowing I am not accidentally upgrading to a version with breaking changes (which hopefully gets a new major version number). Thanks!

Important sidenote: Me and my friends are loving this app!

Future Implementation (Screenshot)

image: ghcr.io/advplyr/audiobookshelf:2

Audiobookshelf Server Version

2.32.1

Current Implementation (Screenshot)

image: ghcr.io/advplyr/audiobookshelf:latest

Originally created by @Sjoerd82 on GitHub (Jan 5, 2026). ### Type of Enhancement None ### Describe the Feature/Enhancement Currently we have the "edge", "latest" and explicit version "2.32.1", etc. tags. Is it possible to add a "2" tag for the latest version 2 major version. Currently set to "latest" but afraid I will accidentaly upgrade to a version that has breaking changes. ### Why would this be helpful? This way I can add this major version to my Docker Compose file, and automatically update by restarting, knowing I am not accidentally upgrading to a version with breaking changes (which hopefully gets a new major version number). Thanks! Important sidenote: Me and my friends are loving this app! ### Future Implementation (Screenshot) image: ghcr.io/advplyr/audiobookshelf:2 ### Audiobookshelf Server Version 2.32.1 ### Current Implementation (Screenshot) image: ghcr.io/advplyr/audiobookshelf:latest
adam added the enhancement label 2026-04-25 00:14:06 +02:00
adam commented 2026-04-25 00:14:06 +02:00
Author
Owner
Copy Link
Copy Source

@nichwall commented on GitHub (Jan 5, 2026):

Currently we have the "edge", "latest" and explicit version "2.32.1", etc. tags. Is it possible to add a "2" tag for the latest version 2 major version. Currently set to "latest" but afraid I will accidentaly upgrade to a version that has breaking changes.

This can also happen whenever any minor or patch version has bugs, not just with the major version number incrementing. I'd recommend you make sure you have regular database backups in general (built into the server) in case of any issues, upgrade or otherwise.

@nichwall commented on GitHub (Jan 5, 2026): > Currently we have the "edge", "latest" and explicit version "2.32.1", etc. tags. Is it possible to add a "2" tag for the latest version 2 major version. Currently set to "latest" but afraid I will accidentaly upgrade to a version that has breaking changes. This can also happen whenever any minor or patch version has bugs, not just with the major version number incrementing. I'd recommend you make sure you have regular database backups in general (built into the server) in case of any issues, upgrade or otherwise.
adam commented 2026-04-25 00:14:06 +02:00
Author
Owner
Copy Link
Copy Source

@Sjoerd82 commented on GitHub (Jan 5, 2026):

I understand this is possible, but in that case it was unplanned to break something, which can always happen. I have backups in place. The major rolling release tag is useful to split off when something is known in advance to break something.

@Sjoerd82 commented on GitHub (Jan 5, 2026): I understand this is possible, but in that case it was unplanned to break something, which can always happen. I have backups in place. The major rolling release tag is useful to split off when something is known in advance to break something.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#3175
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?