Files
6a87848c45 [MM-70140] Remove experimental AD/LDAP login button color settings (#37855)
* [MM-70140] Remove experimental AD/LDAP login button color settings

Remove the dead-code LdapSettings.LoginButtonColor / LoginButtonBorderColor /
LoginButtonTextColor experimental settings. These values were plumbed into the
client config but never consumed by the web or mobile clients, so no AD/LDAP
login button was ever rendered or colored.

Removes the fields from the server config struct and defaults, the client
config payload, the Admin Console Experimental Features section, the webapp
config type, related en.json strings, API definitions, docs, and test/default
config fixtures.

Co-authored-by: mattermost-code <[email protected]>

* [MM-70140] Add test guarding removal of LDAP login button color keys

Assert that GenerateLimitedClientConfig still emits LdapLoginFieldName under an
LDAP license but never emits the removed LdapLoginButtonColor/BorderColor/
TextColor keys, guarding against reintroduction of the dead settings.

Co-authored-by: mattermost-code <[email protected]>

* [MM-70140] Remove LDAP login button colors from webapp LdapSettings type

Keep AdminConfig LdapSettings in sync with the server model after the
experimental AD/LDAP login button color settings were removed.

Co-authored-by: mattermost-code <[email protected]>

* [MM-70140] Update admin console index test after LDAP color removal

Drop experimental/features from the ldap search expectation now that
the AD/LDAP login button color settings are no longer under Experimental.

Co-authored-by: mattermost-code <[email protected]>

* Address PR feedback: remove test for removed LDAP login button color settings

Per @lieut-data's review, drop TestGenerateLimitedClientConfigOmitsLdapLoginButtonColors;
there's no need to perpetually test that a removed feature stays removed.

* chore: retrigger CI after GitHub Actions service outage

Co-authored-by: mattermost-code <[email protected]>

* chore: retrigger CI after Actions service recovery

Co-authored-by: mattermost-code <[email protected]>

---------

Co-authored-by: mattermost-code <[email protected]>
Co-authored-by: mattermost-build <[email protected]>

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-10 10:26:19 -03:00
..
…

About this folder

This folder contains some files that we use to build the mattermost-server and other files like privacy policy and licenses.

The Dockerfile in this folder (Dockerfile.buildenv) is the build environment for our current builds you can find the docker image to download here or build your own.

Docker Image for building the Server

We have a docker image to build mattermost-server and it is based on Go docker image.

In our Docker Hub Repository we have the following images:

  • mattermost/mattermost-build-server:dec-7-2018 which is based on Go 1.11 you can use for MM versions <= 5.8.0
  • mattermost/mattermost-build-server:feb-28-2019 which is based on Go 1.12 you can use for MM versions >= 5.9.0 <= 5.15.0
  • mattermost/mattermost-build-server:sep-17-2019 which is based on Go 1.12.9 you can use for MM versions >= 5.16.0
  • mattermost/mattermost-build-server:20200322_golang-1.14.1 which is based on Go 1.14.1 you can use for MM versions >= 5.24.x
  • mattermost/mattermost-build-server:20201023_golang-1.14.6 which is based on Go 1.14.6 you can use for MM versions >= 5.25.x
  • mattermost/mattermost-build-server:20201119_golang-1.15.5 which is based on Go 1.15.5 you can use for MM versions >= 5.26.x to 5.37.x
  • mattermost/mattermost-build-server:20210810_golang-1.16.7 which is based on Go 1.16.X you can use for MM versions >= 5.38.x