# Automatic updates

**URL:** <https://forum.mattermost.com/t/automatic-updates/4182>\
**Category:** Feedback\
**Created:** [November 29, 2017, 9:56pm UTC](https://forum.mattermost.com/t/automatic-updates/4182 "2017-11-29T21:56:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jared](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/jared/32/1719_2.png) [@jared](https://forum.mattermost.com/u/jared)\
**Post date:** [November 29, 2017, 9:56pm UTC](https://forum.mattermost.com/t/automatic-updates/4182/1 "2017-11-29T21:56:21Z")

</div>

Hi all,

I would like the ability to automatically update mattermost server to the latest version, on the condition that there are no breaking changes so that security issues are automatically resolved/patched.

I can easily script (eg in bash) this to happen but I would like a native solution from mattermost.

---

<div class="post-metadata">

**Author:** ![lindy65](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/lindy65/32/1811_2.png) [@lindy65](https://forum.mattermost.com/u/lindy65)\
**Post date:** [December 4, 2017, 7:56am UTC](https://forum.mattermost.com/t/automatic-updates/4182/2 "2017-12-04T07:56:11Z")

</div>

Hi @jared,

Thanks for your feedback,

We have a Desktop App PR ready for testing linked to [this forum issue](https://mattermost.uservoice.com/forums/306457-general/suggestions/13611411-auto-update-desktop-app-at-least-update-informati).

Could we have your help opening a feature request for automatic updates in the browser and posting a link back here?

---

<div class="post-metadata">

**Author:** ![UgoCloutier](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/ugocloutier/32/1153_2.png) [@UgoCloutier](https://forum.mattermost.com/u/UgoCloutier)\
**Post date:** [February 12, 2019, 8:30pm UTC](https://forum.mattermost.com/t/automatic-updates/4182/3 "2019-02-12T20:30:14Z")

</div>

Is this going to be implemented? I can’t believe this is still no auto-upgrade feature!

---

<div class="post-metadata">

**Author:** ![dannymohammad](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/dannymohammad/32/2489_2.png) [@dannymohammad](https://forum.mattermost.com/u/dannymohammad)\
**Post date:** [February 13, 2019, 3:18am UTC](https://forum.mattermost.com/t/automatic-updates/4182/4 "2019-02-13T03:18:24Z")

</div>

Hello, @UgoCloutier

Throughout my observation, there is always a caveat to auto upgrades in general. For example:

> on the condition that there are no breaking changes so that security issues are automatically resolved/patched

There are **known issues** that some users can live with and vice versa based on the [Mattermost Changelog](https://docs.mattermost.com/administration/changelog.html). Hence, the reason why manual upgrade is preferred most of the time. Let us not forget that it is always a good practice to have [backup](https://docs.mattermost.com/administration/backup.html) before upgrading a system as well that some would overlook at times.

Unless there is a script available that can perform checks against the changelog for specific keywords for the latest version \>\> auto backup the instance (database, config.json, file store) \>\> auto upgrade the Mattermost server (basically all the steps listed in [Upgrading Mattermost Server](https://docs.mattermost.com/administration/upgrade.html)), that will be pretty awesome. 😃

---

<div class="post-metadata">

**Author:** ![JtheBAB](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/jthebab/32/2702_2.png) [@JtheBAB](https://forum.mattermost.com/u/JtheBAB)\
**Post date:** [February 13, 2019, 6:12am UTC](https://forum.mattermost.com/t/automatic-updates/4182/5 "2019-02-13T06:12:51Z")

</div>

@UgoCloutier

[https://github.com/mattermost/docs/pull/2502](https://github.com/mattermost/docs/pull/2502)