v4.0.8

New in v4.0.8

This is a bug fix release that contains fixes for folks who were experiencing issues with migrations (integrity violations due to old foreign keys) and for those who were experiencing an issue where forms would redirect back to the dashboard instead of redisplaying the form when it failed validation.

(The reason for that dashboard redirect was a setting in the new Referral-Policy middleware that was too strict, causing some browsers to force the redirect to the dashboard instead of the the previous page with errors highlighted.)

This release also contains some fixes for the installer.sh, and some improvements to the experimental upgrade script.

• General cleanup and get ubuntu install working. (#4118)
• Set referrer policy to same origin - should fix a lot of weird validation failure behaviors
• Workaround to fix #4117

View more details about what's new in v4 here.

Known Issues

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.

v4.0.7

New in v4.0.7

This is a bug fix release that contains additional fixes for folks running Snipe-IT in a subdirectory, in addition to some license routing fixes and some settings that were making non-required fields required.

• Added content security middleware (experimental)
• Fixes #4075 - this is janky and should be revisited
• Fixes #4069 - include request handler
• Fixes all assets showing as unassigned in license checkout
• Fix box title in Label settings view (#4111)
• Fixes #4096 - various installer issues.

View more details about what's new in v4 here.

Known Issues

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.

v4.0.6

New in v4.0.6

This is a bug fix release.

• Fixes #4061 - bulk checkout error
• Fixes #4020 - fixes searching by username
• Fixes #4051 - use delete method for deleting user files
• Fixes #4011 - do not send email to user on license checkout
• Fixes #4067 - Make unrequired custom fields nullable

View more details about what's new in v4 here.

Known Issues

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.

v4.0.5

New in v4.0.5

This is a bug fix release.

• Fixes #4059 - accessories view
• Fixes #4056 - check for assets before deleting user
• Fix old route (#4053)
• Fixes #4057 - sig file in lightbox
• Fixes #4034 - save login note
• Fixes #4043 - standardize groups API response
• Fixes #3113 and #4040
• Fixes #4027 - proper redirect on fieldset delete
• Experimental simple upgrade script
• Adds rel="noopener" to footer links
• Added referrer-policy header

View more details about what's new in v4 here.

Known Issues

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.

v4.0.4

New in v4.0.4

This is a minor point-release fixes the forgotten password link.

View more details about what's new in v4 here.

Known Issues

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.

v4.0.3

New in v4.0.3

This is a minor point-release that clears the audit input field to make auditing via a barcode scanner easier.

View more details about what's new in v4 here.

Known Issues

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.

v4.0.1

New in v4.0.1

This is a minor point-release to fix an issue with Snipe-IT installs in subdirectories not using the correct URL path from the APP_URL, and fixes an issue with the requestable assets page crashing under certain data circumstances.

View more details about what's new in this release here.

Known Issues

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.

v4.0

New in v4.0

In addition to a robust REST API, we've made countless UI improvements, including the long-awaited ability to edit custom fields, and the ability to bulk-edit users.

We've also upgraded the underlying framework that Snipe-IT is built on, and added more security features, such as the ability to prevent users from picking really bad passwords and enforcing some basic password complexity rules.

Snipe-IT v4 introduces a new "audit" feature, which will allow you to mark an asset as having been physically audited and confirmed to be where it was supposed to be.

Additionally, we've made this audit system super easy to use with a barcode scanner. Just scan in the asset tag on the bulk audit page, and you can audit one after another in lightning speed.

View more details about what's new in this release here.

Known Issues

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.

Upgrading from v3

Please see the upgrade instructions here.

v4.0-beta6

New in v4.0-beta 6

This pre-release contains a few fixes for the importer and how it handles custom fields.

Remember to run:

php composer.phar install --no-dev --prefer-source
php composer.phar dump-autoload
php artisan view:clear
php artisan cache:clear
php artisan config:clear
php artisan migrate

If it exists, you may delete the bootstrap/cache/compiled.php file. It is no longer used.

Important Note on Upgrading

THIS IS A BETA RELEASE. BACK UP YOUR APP KEY AND DATABASE FIRST.

If you are upgrading from a 3.x version of Snipe-IT, your app key was generated using the (deprecated) mcrypt library. Snipe-IT 4.x defaults to using an OpenSSL cipher instead of mcrypt - which will cause no issues if you are installing for the first time, but if you're upgrading, you may get a cipher error. If this happens, do the following:

• open your .env file and add a new field called LEGACY_APP_KEY= and add your existing APP_KEY value there.
• run php artisan config:cache to clear your config cache
• run php artisan snipeit:legacy-recrypt
• run php artisan key:generate to generate a new, non-mcrypt APP_KEY
• clear your browser cookies

You MUST make sure you've backed up your original APP_KEY. The recrypter attempts to use mcrypt to decrypt any encrypted custom fields you have. If you do not run the recrypter and you change your APP_KEY, it will:

• make any encrypted fields undecryptable
• make your LDAP password undecryptable
• void all browser sessions

v4.0-beta5

New in v4.0-beta 5

This pre-release contains many improvements to API consistency from the previous betas, in addition to some smaller bugfixes and UI improvements.

Remember to run:

php composer.phar install --no-dev --prefer-source
php composer.phar dump-autoload
php artisan view:clear
php artisan cache:clear
php artisan config:clear
php artisan migrate

If it exists, you may delete the bootstrap/cache/compiled.php file. It is no longer used.

Important Note on Upgrading

THIS IS A BETA RELEASE. BACK UP YOUR APP KEY AND DATABASE FIRST.

If you are upgrading from a 3.x version of Snipe-IT, your app key was generated using the (deprecated) mcrypt library. Snipe-IT 4.x defaults to using an OpenSSL cipher instead of mcrypt - which will cause no issues if you are installing for the first time, but if you're upgrading, you may get a cipher error. If this happens, do the following:

• open your .env file and add a new field called LEGACY_APP_KEY= and add your existing APP_KEY value there.
• run php artisan config:cache to clear your config cache
• run php artisan snipeit:legacy-recrypt
• run php artisan key:generate to generate a new, non-mcrypt APP_KEY
• clear your browser cookies

You MUST make sure you've backed up your original APP_KEY. The recrypter attempts to use mcrypt to decrypt any encrypted custom fields you have. If you do not run the recrypter and you change your APP_KEY, it will:

• make any encrypted fields undecryptable
• make your LDAP password undecryptable
• void all browser sessions