Upgrade Guide¶
This guide explains how to upgrade your Mattermost deployment across versions and editions.
To start, select one of the following guides:
Upgrade Team Edition¶
Upgrade Team Edition to 3.1.x and later¶
- Download the appropriate next upgrade of your Team Edition server and note any compatibility procedures
- Run
platform -version
to check the current version of your Mattermost server - Determine the appropriate next upgrade for your server:
- Mattermost
v3.0.x
and later can upgrade directly to Mattermostv3.5.x
- Note: If public links are enabled, upgrading from
v3.3.x
and earlier tov3.4.x
and later will invalidate existing public links due to a security upgrade allowing admins to invalidate links by resetting a public link salt from the System Console. - Note: RHEL6 and Ubuntu installations must verify the line
limit nofile 50000 50000
is included in/etc/init/mattermost.conf
file. See the installation guide for your operating system for more details. - Note: RHEL7 and Debian installations must verify the line
LimitNOFILE=49152
is included in the/etc/systemd/system/mattermost.service
file. See the installation guide for your operating system for more details.
- Note: If public links are enabled, upgrading from
- Mattermost
v2.2.x
can upgrade directly tov3.1.x
orv3.2.x
but must follow the extended upgrade guide forv3.0.x
- Mattermost
v2.1.x
and below must follow the process to upgrade tov3.0.x
before upgrading further
- Mattermost
- Use the Version Archive table to find the
[RELEASE URL]
for your desired version and enterwget [RELEASE URL]
to download. For example, to downloadvX.X.X
, usewget https://releases.mattermost.com/X.X.X/mattermost-team-X.X.X-linux-amd64.tar.gz
. - Review Compatibility section in CHANGELOG for the version downloaded and make sure to follow any instructions.
- Run
- Stop the Mattermost Server
- Consider posting an announcement to active teams about stopping the Mattermost server for an upgrade.
- To stop the server run
sudo stop mattermost
.
- Backup your data
- Back up your
config.json
file, which contains your system configuration. This will be used to restore your current settings after the new version is installed. - Backup your database using your organization’s standard procedures for backing up MySQL or PostgreSQL.
- If you’re using local file storage, back up the location where files are stored.
- Back up your
- Install new version
- Run
tar -xvzf mattermost-team-X.X.X-linux-amd64.tar.gz
to decompress the upgraded version and replace the current version of Mattermost on disk, whereX.X.X
is the version number to which you are upgrading.
- Run
- Restore the state of your server
- Copy the backed up version of
config.json
in place of the defaultconfig.json
.
- Copy the backed up version of
- Start your server and address any setting changes relevant in the latest version of Mattermost
- Run
sudo start mattermost
. - Opening the System Console and saving a change will upgrade your
config.json
schema to the latest version using default values for any new settings added.
- Run
- Test the system is working by going to the URL of an existing team. You may need to refresh your Mattermost browser page in order to get the latest updates from the upgrade.
Upgrade Team Edition to 3.0.x¶
Mattermost 3.0 lets users maintain a single account across multiple teams on a Mattermost server. This means one set of credentials, one place to configure all account settings, and a more streamlined sign-up and team joining process.
Special instructions for 2.x servers with duplicate accounts¶
If your Mattermost server has duplicate accounts (users with multiple accounts in multiple teams with the same email address or username), you need to understand the 3.0 upgrade process in detail and take special steps to upgrade successfully.
- Download Mattermost Team Edition 3.0.3
- Run
platform -version
to confirm the current version of your Mattermost server isv2.2.0
,v2.1.0
, orv2.0.0
. If not, please upgrade tov2.0.0
. - Run
wget https://releases.mattermost.com/X.X.X/mattermost-team-X.X.X-linux-amd64.tar.gz
to download the appropriate new version.
- Run
- Stop the Mattermost Server
- Consider posting an announcement to active teams about stopping the Mattermost server for an upgrade
- To stop the server run
sudo stop mattermost
- Backup your data
- Back up your
config.json
file, which contains your system configuration. This will be used to restore your current settings after the new version is installed. - Backup your database using your organization’s standard procedures for backing up MySQL or PostgreSQL.
- If you’re using local file storage, back up the location where files are stored. This location is specified in the
config.json
file underFileSettings
>Directory
. - Verify your backups are successful.
- Back up your
- Install new version
- Double check that your database and configuration file has been backed up, as the database upgrade to 3.x from 2.x cannot be reversed.
- Run
tar -xvzf mattermost-team-X.X.X-linux-amd64.tar.gz
to decompress the upgraded version and replace the current version of Mattermost on disk, whereX.X.X
is the version number to which you are upgrading.
- Restore the state of your server
- Copy the backed up version of
config.json
in place of the defaultconfig.json
. - If you’re using local file storage, restore the data you backed up before running the server. Keep the backup until you’re sure the upgrade has succeeded.
- Copy the backed up version of
- Upgrade your database
- Run
./platform -upgrade_db_30
to upgrade your database from 2.x to 3.x- You may need to run with
sudo -u linux_user_account ./platform -upgrade_db_30
if you’ve setup Mattermost to run under a different account. This will ensure files under./data/
have the correct permissions. - You will be asked
Have you performed a database backup? (YES/NO):
- If you have not backed up your database, enter
NO
and then backup your database - If you have verified your database has been backed up, enter
YES
- If you have not backed up your database, enter
- You will be asked to select a
primary team
.- If you only have one team, enter the name of the team.
- If you have more than one team, specify the
primary team
based on the team you use the most.- If your server contains duplicate accounts (multiple accounts with either the same email addresses or the same usernames) the user account in the
primary team
will be considered the primary account and remain unchanged.- When the server finds a duplicate account not in the
primary team
the email address of the account may be changed to avoid conflicts- An account with a duplicate email address will be updated so
+[TEAM_URL_NAME]
is appended to the local part of the email address. For example: An account with a duplicate emailsteve@company.com
in the team at URLhttps://mattermost.company.com/marketing
becomessteve+marketing@company.com
. The+marketing
used in this procedure is part of the RFC5233 email specification and most email systems will properly routesteve+marketing@company.com
tosteve@company.com
. After the upgrade, if email authentication is used for sign-in, the user would need to sign-in with the new email address. - An account with a duplicate username will be updated so
[TEAM_URL_NAME].
” is prepended to the username. For example: An account with a duplicate usernamesteve
in the team at URLhttps://mattermost.company.com/marketing
becomesmarketing.steve
.
- An account with a duplicate email address will be updated so
- When the server finds a duplicate account not in the
- If your server contains duplicate accounts (multiple accounts with either the same email addresses or the same usernames) the user account in the
- Users with accounts containing duplicate emails or usernames will receive a notification email explaining the upgrade, and instructions on how to move to a single user account (see example)
- You may need to run with
- Run
- Start your server and address any setting changes relevant in the latest version of Mattermost
- Run
sudo start mattermost
. - Opening the System Console and saving a change will upgrade your
config.json
schema to the latest version using default values for any new settings added.
- Run
- Test the system is working by going to the URL of an existing team.
- You may need to refresh your Mattermost browser page in order to get the latest updates from the upgrade.
- After the Mattermost 3.0 upgrade users with duplicate accounts can follow instructions in the upgrade email they received to login to teams on which the duplicate accounts were created and add their primary account to the team and any private groups that are still actively used. Users can continue to access the direct message history of their duplicate accounts using their updated email addresses.
Upgrade Team Edition for 2.2.x and earlier¶
- Download the appropriate next upgrade of your Team Edition server and note any compatibility procedures
- Run
platform -version
to check the current version of your Mattermost server - Determine the appropriate next upgrade for your server:
- Mattermost
v2.0.x
andv2.1.x
can upgrade directly to Mattermostv2.2.x
. - Mattermost
v1.4.x
andv2.0.x
can upgrade directly to Mattermostv2.1.x
. - Mattermost
v1.2.x
must upgrade to Mattermostv1.3.x
before further upgrades. - Mattermost
v1.1.x
must upgrade to Mattermostv1.2.x
before further upgrades. - Mattermost
v1.0.x
must upgrade to Mattermostv1.1.x
before further upgrades.
- Mattermost
- Use the Version Archive List to find the
[RELEASE URL]
for your desired version and enterwget [RELEASE URL]
to download. For example, to downloadvX.X.X
, usewget https://releases.mattermost.com/X.X.X/mattermost-team-X.X.X-linux-amd64.tar.gz
. - Review Compatibility section in CHANGELOG for the version downloaded and make sure to follow any instructions.
- Run
- Stop the Mattermost Server
- Consider posting an announcement to active teams about stopping the Mattermost server for an upgrade.
- To stop the server run
sudo stop mattermost
.
- Backup your data
- Back up your
config.json
file, which contains your system configuration. This will be used to restore your current settings after the new version is installed. - Backup your database using your organization’s standard procedures for backing up MySQL or PostgreSQL.
- If you’re using local file storage, back up the location where files are stored.
- Back up your
- Install new version
- Run
tar -xvzf mattermost-team-X.X.X-linux-amd64.tar.gz
to decompress the upgraded version and replace the current version of Mattermost on disk, whereX.X.X
is the version number to which you are upgrading.
- Run
- Restore the state of your server
- Copy the backed up version of
config.json
in place of the defaultconfig.json
.
- Copy the backed up version of
- Start your server and address any setting changes relevant in the latest version of Mattermost
- Run
sudo start mattermost
. - Opening the System Console and saving a change will upgrade your
config.json
schema to the latest version using default values for any new settings added.
- Run
- Test the system is working by going to the URL of an existing team. You may need to refresh your Mattermost browser page in order to get the latest updates from the upgrade.
Upgrade Team Edition to Enterprise Edition¶
- Confirm you have the latest version of Mattermost Team Edition installed
- Run
platform -version
to check the current version of your Mattermost server and compare the version with the latest release listed on https://mattermost.org/download. - If it is not the latest release, upgrade to the latest release.
- Run
- Follow the Enterprise Edition upgrade procedure to replace the Team Edition binary with the latest Mattermost Enterprise Edition build (in the format
https://releases.mattermost.com/X.X.X/mattermost-X.X.X-linux-amd64.tar.gz
). - Run
platform -version
to confirm the latest Enterprise Edition version has been successfully installed. - In the System Console, go to OTHER > Edition and License > License Key and upload the license key file you received via email.
- Reset the Mattermost account as the directory owner by typing:
sudo chown -R mattermost:mattermost <path-to-your-mattermost-folder>
sudo chmod -R g+w <path-to-your-mattermost-folder>
- To ensure client applications don’t encounter issues with out-of-sync caches, you can force clients to refresh after a server upgrade by changing any setting in the System Console. For example, go to System Console > General > Configuration, and copy the Listen Address. Then paste the Listen Address back into the field, and press Save.
The Edition and License sections on the page should update to confirm your system has been updated to the Enterprise Edition.
For any issues, Mattermost Enterprise Edition subscribers and trial license users can email support@mattermost.com
Upgrade Enterprise Edition¶
Upgrade Enterprise Edition to 3.1.x and later¶
- Download the appropriate next upgrade of your Team Edition server and note any compatibility procedures
- Run
platform -version
to check the current version of your Mattermost server - Determine the appropriate next upgrade for your server:
- Mattermost
v3.0.x
and later can upgrade directly to Mattermostv3.5.x
- Note: If public links are enabled, upgrading from
v3.3.x
and earlier tov3.4.x
and later will invalidate existing public links due to a security upgrade allowing admins to invalidate links by resetting a public link salt from the System Console. - Note: RHEL6 and Ubuntu installations must verify the line
limit nofile 50000 50000
is included in/etc/init/mattermost.conf
file. See the installation guide for your operating system for more details. - Note: RHEL7 and Debian installations must verify the line
LimitNOFILE=49152
is included in the/etc/systemd/system/mattermost.service
file. See the installation guide for your operating system for more details.
- Note: If public links are enabled, upgrading from
- Mattermost
v2.2.x
can upgrade directly tov3.1
orv3.2
but must follow the extended upgrade guide forv3.0.x
- Note: For
v3.2.x
only,"BindUsername"
, and"BindPassword"
underLdapSettings
are required fields with anonymous bind not supported. Forv3.2.x
andv3.3.x
only,"FirstNameAttribute"
and"LastNameAttribute"
underLdapSettings
are required fields.
- Note: For
- Mattermost
v2.1.x
and below must follow the process to upgrade tov3.0.x
before upgrading further
- Mattermost
- Use the Version Archive List to find the
[RELEASE URL]
for your desired version and enterwget [RELEASE URL]
to download. For example, to downloadvX.X.X
, usewget https://releases.mattermost.com/X.X.X/mattermost-X.X.X-linux-amd64.tar.gz
. - Review Compatibility section in CHANGELOG for the version downloaded and make sure to follow any instructions.
- Run
- Stop the Mattermost Server
- Consider posting an announcement to active teams about stopping the Mattermost server for an upgrade.
- To stop the server run
sudo stop mattermost
.
- Backup your data
- Back up your
config.json
file, which contains your system configuration. This will be used to restore your current settings after the new version is installed. - Backup your database using your organization’s standard procedures for backing up MySQL or PostgreSQL.
- If you’re using local file storage, back up the location where files are stored.
- Back up your
- Install new version
- Run
tar -xvzf mattermost-X.X.X-linux-amd64.tar.gz
to decompress the upgraded version and replace the current version of Mattermost on disk, whereX.X.X
is the version number to which you are upgrading.
- Run
- Restore the state of your server
- Copy the backed up version of
config.json
in place of the defaultconfig.json
.
- Copy the backed up version of
- Start your server and address any setting changes relevant in the latest version of Mattermost
- Run
sudo start mattermost
. - Opening the System Console and saving a change will upgrade your
config.json
schema to the latest version using default values for any new settings added.
- Run
- Test the system is working by going to the URL of an existing team. You may need to refresh your Mattermost browser page in order to get the latest updates from the upgrade.
Upgrade to Enterprise Edition 3.0.x¶
Mattermost 3.0 lets users maintain a single account across multiple teams on a Mattermost server. This means one set of credentials, one place to configure all account settings, and a more streamlined sign-up and team joining process.
Special instructions for 2.x servers with duplicate accounts¶
If your Mattermost server has duplicate accounts (users with multiple accounts in multiple teams with the same email address or username), you need to understand the 3.0 upgrade process in detail and take special steps to upgrade successfully.
- Download Mattermost Enterprise Edition 3.0.3
- Run
platform -version
to confirm the current version of your Mattermost server isv2.2.0
,v2.1.1
, orv2.0.0
of either Mattermost Enteprrise Edition or Mattermost Team Edition. If not, please upgrade to at least Mattermost Enterprise Editionv2.0.0
. - Run
wget https://releases.mattermost.com/X.X.X/mattermost-X.X.X-linux-amd64.tar.gz
to download the appropriate new version.
- Run
- Stop the Mattermost Server
- Consider posting an announcement to active teams about stopping the Mattermost server for an upgrade
- To stop the server run
sudo stop mattermost
- Backup your data
- Back up your
config.json
file, which contains your system configuration. This will be used to restore your current settings. after the new version is installed. - Backup your database using your organization’s standard procedures for backing up MySQL or PostgreSQL.
- If you’re using local file storage, back up the location where files are stored.
- Verify your backups are successful.
- Back up your
- Install new version
- Double check that your database and configuration file has been backed up, as the database upgrade to 3.x from 2.x cannot be reversed.
- Run
tar -xvzf mattermost-X.X.X-linux-amd64.tar.gz
to decompress the upgraded version and replace the current version of Mattermost on disk, whereX.X.X
is the version number to which you are upgrading.
- Restore the state of your server
- Copy the backed up version of
config.json
in place of the defaultconfig.json
.
- Copy the backed up version of
- Upgrade your database
- Run
./platform -upgrade_db_30
to upgrade your database from 2.x to 3.x- You may need to run with
sudo -u linux_user_account ./platform -upgrade_db_30
if you’ve setup Mattermost to run under a different account. This will ensure files under./data/
have the correct permissions. - You will be asked
Have you performed a database backup? (YES/NO):
- If you have not backed up your database, enter
NO
and then backup your database - If you have verified your database has been backed up, enter
YES
- If you have not backed up your database, enter
- You will be asked to select a
primary team
.- If you only have one team, enter the name of the team.
- If you have more than one team, specify the
primary team
based on the team you use the most.- If your server contains duplicate accounts (multiple accounts with either the same email addresses or the same usernames) the user account in the
primary team
will be considered the primary account and remain unchanged.- When the server finds a duplicate account not in the
primary team
the email address of the account may be changed to avoid conflicts- An account with a duplicate email address will be updated so
+[TEAM_URL_NAME]
is appended to the local part of the email address. For example: An account with a duplicate emailsteve@company.com
in the team at URLhttps://mattermost.company.com/marketing
becomessteve+marketing@company.com
. The+marketing
used in this procedure is part of the RFC5233 email specification and most email systems will properly routesteve+marketing@company.com
tosteve@company.com
. After the upgrade, if email authentication is used for sign-in, the user would need to sign-in with the new email address. - An account with a duplicate username will be updated so
[TEAM_URL_NAME].
” is prepended to the username. For example: An account with a duplicate usernamesteve
in the team at URLhttps://mattermost.company.com/marketing
becomesmarketing.steve
.
- An account with a duplicate email address will be updated so
- When the server finds a duplicate account not in the
- If your server contains duplicate accounts (multiple accounts with either the same email addresses or the same usernames) the user account in the
- Users with accounts containing duplicate emails or usernames will receive a notification email explaining the upgrade, and instructions on how to move to a single user account (see example)
- You may need to run with
- Run
- Start your server and address any setting changes relevant in the latest version of Mattermost
- Run
sudo start mattermost
. - Opening the System Console and saving a change will upgrade your
config.json
schema to the latest version using default values for any new settings added.
- Run
- Test the system is working by going to the URL of an existing team.
- You may need to refresh your Mattermost browser page in order to get the latest updates from the upgrade.
- After the Mattermost 3.0 upgrade users with duplicate accounts can follow instructions in the upgrade email they received to login to teams on which the duplicate accounts were created and add their primary account to the team and any private groups that are still actively used. Users can continue to access the direct message history of their duplicate accounts using their updated email addresses.
For any issues, Mattermost Enterprise Edition subscribers and trial license users can email support@mattermost.com
Upgrade Enterprise Edition to 2.2.x and earlier¶
- Download the appropriate next upgrade of your Enterprise Edition server and note any compatibility procedures
- Run
platform -version
to check the current version of your Mattermost server - Determine the appropriate next upgrade for your server:
- Mattermost
v2.0.x
andv2.1.x
can upgrade directly to Mattermostv2.2.x
. - Mattermost
v1.4.x
andv2.0.x
can upgrade directly to Mattermostv2.1.x
. - Mattermost
v1.2.x
must upgrade to Mattermostv1.3.x
before further upgrades. - Mattermost
v1.1.x
must upgrade to Mattermostv1.2.x
before further upgrades. - Mattermost
v1.0.x
must upgrade to Mattermostv1.1.x
before further upgrades.
- Mattermost
- Use the Version Archive List to find the
[RELEASE URL]
for your desired version and enterwget [RELEASE URL]
to download. For example, to downloadvX.X.X
, usewget https://releases.mattermost.com/X.X.X/mattermost-X.X.X-linux-amd64.tar.gz
. - Review Compatibility section in CHANGELOG for the version downloaded and make sure to follow any instructions.
- Run
- Stop the Mattermost Server
- Consider posting an announcement to active teams about stopping the Mattermost server for an upgrade.
- To stop the server run
sudo stop mattermost
.
- Backup your data
- Back up your
config.json
file, which contains your system configuration. This will be used to restore your current settings after the new version is installed. - Backup your database using your organization’s standard procedures for backing up MySQL or PostgreSQL.
- If you’re using local file storage, back up the location where files are stored.
- Back up your
- Install new version
- Run
tar -xvzf mattermost-X.X.X-linux-amd64.tar.gz
to decompress the upgraded version and replace the current version of Mattermost on disk, whereX.X.X
is the version number to which you are upgrading.
- Run
- Restore the state of your server
- Copy the backed up version of
config.json
in place of the defaultconfig.json
.
- Copy the backed up version of
- Start your server and address any setting changes relevant in the latest version of Mattermost
- Run
sudo start mattermost
. - Opening the System Console and saving a change will upgrade your
config.json
schema to the latest version using default values for any new settings added.
- Run
- Test the system is working by going to the URL of an existing team. You may need to refresh your Mattermost browser page in order to get the latest updates from the upgrade.
For any issues, Mattermost Enterprise Edition subscribers and trial license users can email support@mattermost.com
Version Archive¶
Mattermost Enterprise Edition Server¶
Private cloud enterprise communications server.
- Free to use in “team mode” with same features as open source version.
- Enterprise features unlock with a license key and purchase of a subscription. See feature list and pricing (including academic and non-profit options).
- Mattermost Enterprise Edition v3.5.1 - View Changelog - Download
https://releases.mattermost.com/3.5.1/mattermost-3.5.1-linux-amd64.tar.gz
- Mattermost Enterprise Edition v3.4.0 - View Changelog - Download
https://releases.mattermost.com/3.4.0/mattermost-3.4.0-linux-amd64.tar.gz
- Mattermost Enterprise Edition v3.3.0 - View Changelog - Download
https://releases.mattermost.com/3.3.0/mattermost-3.3.0-linux-amd64.tar.gz
- Mattermost Enterprise Edition v3.2.0 - View Changelog - Download
https://releases.mattermost.com/3.2.0/mattermost-3.2.0-linux-amd64.tar.gz
- Mattermost Enterprise Edition v3.1.0 - View Changelog - Download
https://releases.mattermost.com/3.1.0/mattermost-3.1.0-linux-amd64.tar.gz
- Mattermost Enterprise Edition v3.0.3 - View Changelog - Download
https://releases.mattermost.com/3.0.3/mattermost-3.0.3-linux-amd64.tar.gz
- Mattermost Enterprise Edition v2.2.0 - View Changelog - Download
https://releases.mattermost.com/2.2.0/mattermost-2.2.0-linux-amd64.tar.gz
- Mattermost Enterprise Edition v2.1.0 - View Changelog - Download
https://releases.mattermost.com/2.1.0/mattermost-2.1.0-linux-amd64.tar.gz
Mattermost Team Edition Server¶
Open source self-hosted team communication server compiled by Mattermost, Inc, available under an MIT license.
- Identical feature set to free version of Mattermost Enterprise Edition, but cannot be unlocked with a license key.
- Mattermost Team Edition v3.5.1 - View Changelog - Download
https://releases.mattermost.com/3.5.1/mattermost-team-3.5.1-linux-amd64.tar.gz
- Mattermost Team Edition v3.4.0 - View Changelog - Download
https://releases.mattermost.com/3.4.0/mattermost-team-3.4.0-linux-amd64.tar.gz
- Mattermost Team Edition v3.3.0 - View Changelog - Download
https://releases.mattermost.com/3.3.0/mattermost-team-3.3.0-linux-amd64.tar.gz
- Mattermost Team Edition v3.2.0 - View Changelog - Download
https://releases.mattermost.com/3.2.0/mattermost-team-3.2.0-linux-amd64.tar.gz
- Mattermost Team Edition v3.1.0 - View Changelog - Download
https://releases.mattermost.com/3.1.0/mattermost-team-3.1.0-linux-amd64.tar.gz
- Mattermost Team Edition v3.0.3 - View Changelog - Download
https://releases.mattermost.com/3.0.3/mattermost-team-3.0.3-linux-amd64.tar.gz
- Mattermost Team Edition v2.2.0 - View Changelog - Download
https://releases.mattermost.com/2.2.0/mattermost-team-2.2.0-linux-amd64.tar.gz
- Mattermost Team Edition v2.1.0 - View Changelog - Download
https://releases.mattermost.com/2.1.0/mattermost-team-2.1.0-linux-amd64.tar.gz
- Mattermost Team Edition v2.0.0 - View Changelog - Download
https://releases.mattermost.com/2.0.0/mattermost-team-2.0.0-linux-amd64.tar.gz
- Mattermost Team Edition v1.4.0 - View Changelog - Download
https://releases.mattermost.com/1.4.0/mattermost-team-1.4.0-linux-amd64.tar.gz
- Mattermost Team Edition v1.3.0 - View Changelog - Download
https://releases.mattermost.com/1.3.0/mattermost-team-1.3.0-linux-amd64.tar.gz
- Mattermost Team Edition v1.2.1 - View Changelog - Download
https://releases.mattermost.com/1.2.1/mattermost-team-1.2.1-linux-amd64.tar.gz
- Mattermost Team Edition v1.1.1 - View Changelog - Download
https://releases.mattermost.com/1.1.1/mattermost-team-1.1.1-linux-amd64.tar.gz
- Mattermost Team Edition v1.1.0 - View Changelog - Download
https://releases.mattermost.com/1.1.0/mattermost-team-1.1.0-linux-amd64.tar.gz
- Mattermost Team Edition v1.0.0 - View Changelog - Download
https://releases.mattermost.com/1.0.0/mattermost-team-1.0.0-linux-amd64.tar.gz
- Mattermost Team Edition v0.7.0 - View Changelog - Download
https://releases.mattermost.com/0.7.0/mattermost-team-0.7.0-linux-amd64.tar.gz
- Mattermost Team Edition v0.6.0 - View Changelog - Download
https://releases.mattermost.com/0.6.0/mattermost-team-0.6.0-linux-amd64.tar.gz
- Mattermost Team Edition v0.5.0 - View Changelog - Download
https://releases.mattermost.com/0.5.0/mattermost-team-0.5.0-linux-amd64.tar.gz