Skip to main content

2026.1.0 to 2026.1.1

1. Preferences: clientHideFloatingActionButton removed​

What changed​

The clientHideFloatingActionButton preference has been removed from the available preferences.

Why it matters​

Projects must no longer rely on clientHideFloatingActionButton as a configurable preference.

Remove references to clientHideFloatingActionButton from project preferences, configuration documentation, and custom upgrade notes.

If a project depended on hiding the Floating Action Button, review whether this behavior is still required. If it is required for accessibility-related reasons, validate the behavior with enableA11y enabled for the affected users.

The enableA11y UserPreference is not a direct replacement for clientHideFloatingActionButton. It controls accessibility-related behavior and can affect the visibility of the Floating Action Button only as part of that accessibility behavior.

2. Authentication: Configure the JWKS endpoint URL for GitLab manually​

What changed​

In version 2026.1.1, automatic determination of the JWKS endpoint URL does not work for GitLab when using the OAuth2 Authorization Code Flow.

Why it matters​

GitLab-based authentication using the OAuth2 Authorization Code Flow cannot retrieve the signing keys automatically when the JWKS endpoint URL is not configured. Token validation may therefore fail.

For every GitLab OAuth2 Authorization Code Flow alias configuration, enter the JWKS endpoint URL manually and verify that the configured URL is reachable.

Information​

This issue is fixed in version 2026.1.2. From this version onward, the JWKS endpoint URL is determined automatically for GitLab.