| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2020-04-02 | Update patch | Caleb Maclennan | |
| 2020-04-02 | Adopt and revamp build | Caleb Maclennan | |
| 2019-09-14 | Update build process to latest master | William Gathoye | |
| 2018-11-12 | Compile Go with PIE and remove unneeded log folder creation | William Gathoye | |
| 2018-07-17 | Fix systemd service | William Gathoye | |
| 2018-07-16 | Upgrade to 5.1.0 and reflect new path changes | William Gathoye | |
| 2018-04-22 | Upgrade to 4.9.0 | William Gathoye | |
| 2017-11-12 | The CARCH variable might be incorrect on ARM64/aarch64 | William Gathoye | |
| 2017-11-11 | Apply PKGBUILD changes from Mattermost package | William Gathoye | |
| 2017-09-24 | Upgrade to 4.2 + fix repo split | William Gathoye | |
| 2017-08-26 | Remove pngquant from build requirements | William Gathoye | |
| 2017-08-14 | The commit id was always the same, fix this. | William Gathoye | |
| We previously used a way to recover the last tag from all branches. However proceeding this way could leads in unattended behaviors. First, imagine we are in the release 4.0, and a bug fix appears for 3.6 afterwardsi. The latest tag is not 4.0.x but 3.6.x and the package is not updated. Second, the manner we were taking the tag was taking its fixed commit with it, not the latest commit available after the tag. Now, we are just using a more common manner to recover the commit id: we are prefixing it with the latest tag reachable from the **current** branch. | |||
| 2017-07-10 | Add note for local tests | William Gathoye | |
| 2017-06-18 | Add yarn dependency | William Gathoye | |
| 2017-05-10 | Initial import from AUR package mattermost and update to 3.9 | William Gathoye | |