[Enhancement]: Have the version number follow YY.MM.subrelease scheme with React rewrite release #3144

Closed
opened 2026-04-25 00:13:54 +02:00 by adam · 2 comments
Owner

Originally created by @ZLoth on GitHub (Dec 8, 2025).

Type of Enhancement

Web Interface/Frontend

Describe the Feature/Enhancement

Currently, the ABS version number is 2.releasenumber.subrelease number. As the React reskinning can be considered a major revision of the Audiobook software, I recommend moving the numbering scheme to YY.MM,subrelease schedule, where YY is the last two digits of the year, MM is a two-digit month, and subrelease is any bug fixes pending a major release.

Why would this be helpful?

This will be helpful in both a troubleshooting aspect as well as identifying when a release occurred.

Future Implementation (Screenshot)

Image

Audiobookshelf Server Version

2.31

Current Implementation (Screenshot)

Image
Originally created by @ZLoth on GitHub (Dec 8, 2025). ### Type of Enhancement Web Interface/Frontend ### Describe the Feature/Enhancement Currently, the ABS version number is 2.releasenumber.subrelease number. As the React reskinning can be considered a major revision of the Audiobook software, I recommend moving the numbering scheme to YY.MM,subrelease schedule, where YY is the last two digits of the year, MM is a two-digit month, and subrelease is any bug fixes pending a major release. ### Why would this be helpful? This will be helpful in both a troubleshooting aspect as well as identifying when a release occurred. ### Future Implementation (Screenshot) <img width="70" height="41" alt="Image" src="https://github.com/user-attachments/assets/c5841505-0f34-48a2-9be0-754e28f542f3" /> ### Audiobookshelf Server Version 2.31 ### Current Implementation (Screenshot) <img width="64" height="41" alt="Image" src="https://github.com/user-attachments/assets/1396f94f-97ec-4c67-ada5-457080294602" />
adam added the enhancement label 2026-04-25 00:13:54 +02:00
adam closed this issue 2026-04-25 00:13:54 +02:00
Author
Owner

@nichwall commented on GitHub (Dec 8, 2025):

We have been using semantic versioning, without having a major release to go to 3.x.x yet.

@nichwall commented on GitHub (Dec 8, 2025): We have been using semantic versioning, without having a major release to go to 3.x.x yet.
Author
Owner

@advplyr commented on GitHub (Dec 8, 2025):

I can see why that versioning would be preferred but we're not going to switch from semantic versioning since the mess that would create isn't worth the minor benefit of seeing a month and year in the version.

@advplyr commented on GitHub (Dec 8, 2025): I can see why that versioning would be preferred but we're not going to switch from semantic versioning since the mess that would create isn't worth the minor benefit of seeing a month and year in the version.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#3144