[Bug]: Branding: "Overview" claims 35.0.1 is Nextcloud Hub 26 Spring, adding to the confusion

[TheWojtek]

⚠️ This issue respects the following points: ⚠️

• This is not a troubleshooting question, general support matter, or webserver/proxy problem, but likely a bug (if unsure, ask the Community Help Forum).
• This issue is not already reported on Github OR solved at the Community Help Forum (I've searched!).
• I'm using a maintained major version of Nextcloud Server and tested against the latest patch level. (Supported major versions and current patch levels).
• I agree to follow Nextcloud's Code of Conduct.
• I've tried my best to provide clear reproduction steps that someone unfamiliar with this bug could use to reproduce it.

Bug description

The "Overview" section of Administration section claims Nextcloud 35.0.1 is "Nextcloud Hub 26 Spring":

This adds to the confusion, initially introduced by NC35.0.0 being offered as the upgrade to 34.0.3, while 34.0.4 was launched at the same time. This led to numerous installations being upgraded to 35 which broke dozens of applications.
This also leads to suspicions about the overall quality of the release.

Steps to reproduce

1. Install 35.0.1 update
2. Navigate to "Administration settings"

Expected behavior

The instance should report the version and flavor in a predictable and correct manner.

Nextcloud Server version

35

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.4

Web server

Apache (supported)

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

Updated from a MINOR version (ex. 32.0.1 to 32.0.2)

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

Irrelevant to the issue

List of activated Apps

Irrelevant to the issue

Nextcloud Signing status

Irrelevant to the issue

Nextcloud Logs

Irrelevant to the issue

Additional info

No response

[szaimen]

Will be fixed with nc35.0.2. See #64758