Update 4.7 to 4.8-Beta introduced breaking changes

[devKazuto 1]

Hey guys,

I've just tried the 4.8.0.55 beta because I wanted to try the new discord plugin but now I can't downgrade back to 4.7 because 4.8 moved, renamed or deleted files that can't be found by 4.7.

This breaks systems and as this is a breaking change it should not be minor version bump but major version bump and this has absolutely nothing to do with being a beta version.

Moving, renaming, and deleting files that older versions depend on is a BC and should be versioned accordingly.

 

log.txt

[GrimReaper 4741]

Downgrade/rollback was never neither recommended nor officially supported, especially between different branches (i.e. 4.8 vs 4.7), nothing new there. Hopefully you have full backup else rebuild is required.

[roaku 842]

42 minutes ago, devKazuto said:

Hey guys,

I've just tried the 4.8.0.55 beta because I wanted to try the new discord plugin but now I can't downgrade back to 4.7 because 4.8 moved, renamed or deleted files that can't be found by 4.7.

This breaks systems and as this is a breaking change it should not be minor version bump but major version bump and this has absolutely nothing to do with being a beta version.

Moving, renaming, and deleting files that older versions depend on is a BC and should be versioned accordingly.

 

log.txt 18.97 kB · 0 downloads

Emby doesn't use semantic versioning.

Any version change should be assumed to be breaking.

[devKazuto 1]

Why use the semantic versioning format instead of just build dates then? This format lets developers and tinkers think semantic versioning is being used.

 

But good to know that every version could be breaking.

Edited October 24, 2023 by devKazuto

[ebr 16185]

That is not a breaking change.  A breaking change would mean something broke when you upgraded.  Rolling back to a previous version with configuration and databases from a newer version would be backward compatibility which we do not support.

[roaku 842]

59 minutes ago, devKazuto said:

Why use the semantic versioning format instead of just build dates then? This format lets developers and tinkers think semantic versioning is being used.

 

But good to know that every version could be breaking.

Ok, let's unpack some things.

First, Semantic Versioning doesn't have its own format. It added semantic meaning to an existing and very popular versioning format. In other word, just because you see xx.yy.zz or xx.yy.zz.bb, doesn't mean its authors' are being semantic.

Second, SemVer isn't really intended for end user releases, in general. It's specifically about releases of apis and libraries that are intended to be used by other programs. It's a way of signalling to other developers that they should or shouldn't expect to have to change *their* code if they switch to a new version of someone else's api or library. Don't expect a packaged end user product to be semantically versioned, even if it contains semantically versioned components under the hood.

Third, SemVer says absolutely nothing about downgrading after an upgrade.

Fourth, never install a beta of anything onto something you care about without having an explicit and tested backup and recovery process in place. Betas are an attempt to find problems before release, so expect to find problems.

 

[Luke 42080]

What made you want to downgrade back to 4.7?

[Luke 42080]

@devKazuto?

[devKazuto 1]

On 24/10/2023 at 22:33, Luke said:

What made you want to downgrade back to 4.7?

Sorry, I've got no notification about your reply.

My library was broken and I was unable to log in to my main account because of the added password requirement. As my main account did not have a password to begin with I was not able to access any administrative settings.

The password requirement does not make any sense to me using Emby in a local environment and is just a unnecessary step for me when sharing devices like a TV with family members, each having their own profile, forcing me to input a space as a password when switching back to my profile.

Edited November 19, 2023 by devKazuto

[Luke 42080]

2 hours ago, devKazuto said:

Sorry, I've got no notification about your reply.

My library was broken and I was unable to log in to my main account because of the added password requirement. As my main account did not have a password to begin with I was not able to access any administrative settings.

The password requirement does not make any sense to me using Emby in a local environment and is just a unnecessary step for me when sharing devices like a TV with family members, each having their own profile, forcing me to input a space as a password when switching back to my profile.

Hi, but your login is remembered so this is only a one-time process, right?

[devKazuto 1]

1 minute ago, Luke said:

Hi, but your login is remembered so this is only a one-time process, right?

Do you mean when switching back from my wifes profile to my profile on a device? No, I have to enter my password every time.

[Luke 42080]

1 minute ago, devKazuto said:

Do you mean when switching back from my wifes profile to my profile on a device? No, I have to enter my password every time.

Hi, what Emby app are you testing with?

[devKazuto 1]

Just now, Luke said:

Hi, what Emby app are you testing with?

I've tested it with Android 3.3.40, Browser and Roku.

[Luke 42080]

2 hours ago, devKazuto said:

I've tested it with Android 3.3.40, Browser and Roku.

How exactly are you switching users?

[devKazuto 1]

Using the menu

 

Edit

Apparently this issue does not appear anymore on the Android or Browser client and only appears on the Roku Client (Channel).

Edited November 20, 2023 by devKazuto

[ebr 16185]

Hi.  The Roku app will be updated just before 4.8 releases.