[Bug]: Webbased updater does not use 'localstorage.umask' settings

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

Using a non-standard umask:

config.php:
.
.
'localstorage.umask' => 0072
.
.

User files are created with permission 604.

Using webbased updater results in permission 640.

File permission 604 ist required at hetzner.com (see https://docs.hetzner.com/konsoleh/general/faq/file-authorization/)

Steps to reproduce

1. Set non-standard umask in config.php
2. Perform nexcloud or app upgrade
3. Check permission

Expected behavior

Correct usage of umask-setting.

Nextcloud Server version

31

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.3

Web server

Apache (supported)

Database engine version

MySQL

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

None

Are you using the Nextcloud Server Encryption module?

Encryption is Enabled

What user-backends are you using?

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

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

Start with the web-based updater flow and how it reads config.php during a Nextcloud or app upgrade, focusing on the localstorage.umask setting. Reproduce the upgrade on Debian/Ubuntu with PHP 8.3 and verify that created files use the configured 604 permission rather than 640.