GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

May 26, 2016

Update Chromium · 69351428

Allan Sandfeld Jensen authored 8 years ago


Pulls in cherry-picked security fixes from Chromium 51.

Change-Id: I4c16b2c8633c53e6c2ae3a6fcdd446bcc404335b
Task-number: QTBUG-53643
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>

2 tags

69351428

May 13, 2016

Add changes file for 5.6.1 · 47031c68

Allan Sandfeld Jensen authored 8 years ago


Change-Id: Ic36c55b5deaceb2a7944f33aead62c6cb31a01f9
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>

47031c68

Admin message