LinuxServer Changes:
Rebasing to alpine 3.9.
snipe-it Changes:
New in v4.6.15
Version 4.6.15 of Snipe-IT is a hotfix release that addresses an issue that users who have two-factor enabled have been experiencing because Google Image Charts turned off their API. (This was apparently announced quite some time ago, but because no API key is required, there wasn't really a super-efficient way of letting third-parties using their library know about it.) The new implementation should work seamlessly with older, already-enrolled devices, and is a more secure way of implementing 2FA, since we generate the QR enrollment barcode locally now, instead of reaching out to Google's API.
If you are using two-factor authentication in your Snipe-IT implementation, you should ABSOLUTELY upgrade as soon as you can.
We'll be rolling this update out to our hosted customers over the next 24 hours.
Developers: this fix has been forward-ported to the develop branch.
Fixed:
- Fixed #6834 and #6402 - skip Google's CharT Image API and generate enrollment QRs locally.
Upgrading
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php.
For a full list of changes, see the changelog.
IMPORTANT: This will be one of the final releases of Snipe-IT that will work with PHP5. Future versions of Snipe-IT will require PHP 7.1.3 or greater. Please start upgrading your versions of PHP to 7.1.3 to prepare for the next major release. There may be a few small bug fix releases before Snipe-IT v5, but you should start preparing now.
Known Issues
Snipe-IT v4.x is not compatible with PHP 7.3. You'll need to use a version of PHP between 5.6.4 and 7.2.x. This is due to a limitation of the underlying framework. The upcoming v5 will support 7.3+.
Users running MariaDB 10.2.7 and later may have an issue upgrading or installing, due to a change in the way MariaDB stores null defaults. This issue will be fixed once the open pull request in the Doctrine repo is merged and a new version of Doctrine is released with these fixes. You can read more about that issue here.
After completing the upgrade process below, be sure to clear your browser cookies.
Upgrading from v3
Please see the upgrade instructions here.