Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 31 million developers.Sign up
New in v4.6.10
This is a tiny release that fixes two bugs that would only affect a select group of users. While we hate to release multiple times in a day, we thought it prudent to get these fixes in your hot little hands as soon as possible, and we only just uncovered and fixed one of these bugs right after the 4.6.9 release went out.
The first issue would only happen for users who have full multiple company support enabled, and are not logged in as a superadmin. In that case, searching in the asset select list (for example, when checking a license out to an asset) would return an error that looks like
Integrity constraint violation: 1052 Column 'company_id' in where clause is ambiguous.
The second issue affected only the
/api/v1/hardware/byserial API endpoint, where we were applying the incorrect permission, so users that were NOT superadmins would get a permissions error.
- Fixed #6367 - pass table name and column_id to
- Fixed #6704 - don’t apply gate to
$arrayscollection, just check that the user can view assets
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run
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.
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.