A free open source IT asset/license management system
AGPL-3.0 License
Bot releases are hidden (Show)
Published by snipe about 7 years ago
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.
View more details about what's new in v4 here.
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.
Please see the upgrade instructions here.
Published by snipe about 7 years ago
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.
View more details about what's new in v4 here.
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.
Please see the upgrade instructions here.
Published by snipe about 7 years ago
This is a bug fix release.
View more details about what's new in v4 here.
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.
Please see the upgrade instructions here.
Published by snipe about 7 years ago
This is a bug fix release.
View more details about what's new in v4 here.
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.
Please see the upgrade instructions here.
Published by snipe about 7 years ago
This is a minor point-release fixes the forgotten password link.
View more details about what's new in v4 here.
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.
Please see the upgrade instructions here.
Published by snipe about 7 years ago
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.
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.
Please see the upgrade instructions here.
Published by snipe about 7 years ago
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.
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.
Please see the upgrade instructions here.
Published by snipe about 7 years ago
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.
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.
Please see the upgrade instructions here.
Published by snipe about 7 years ago
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.
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:
LEGACY_APP_KEY=
and add your existing APP_KEY value there.php artisan config:cache
to clear your config cachephp artisan snipeit:legacy-recrypt
php artisan key:generate
to generate a new, non-mcrypt APP_KEYYou 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:
Published by snipe about 7 years ago
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.
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:
LEGACY_APP_KEY=
and add your existing APP_KEY value there.php artisan config:cache
to clear your config cachephp artisan snipeit:legacy-recrypt
php artisan key:generate
to generate a new, non-mcrypt APP_KEYYou 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:
Published by snipe about 7 years ago
This pre-release contains many improvements to API consistency from the previous alphas, in addition to some smaller bugfixes and UI improvements. See the complete changelog here.
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.
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:
LEGACY_APP_KEY=
and add your existing APP_KEY value there.php artisan config:cache
to clear your config cachephp artisan snipeit:recrypter
php artisan key:generate
to generate a new, non-mcrypt APP_KEYYou 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:
Published by snipe about 7 years ago
This pre-release contains many improvements to API consistency from the previous alphas, in addition to some smaller bugfixes and UI improvements. See the complete changelog here.
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.
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:
LEGACY_APP_KEY=
and add your existing APP_KEY value there.php artisan config:cache
to clear your config cachephp artisan snipeit:recrypter
php artisan key:generate
to generate a new, non-mcrypt APP_KEYYou 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:
Published by snipe about 7 years ago
This pre-release contains many improvements to API consistency from the previous alphas, in addition to some smaller bugfixes and UI improvements. See the complete changelog here.
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.
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:
LEGACY_APP_KEY=
and add your existing APP_KEY value there.php artisan config:cache
to clear your config cachephp artisan snipeit:recrypter
php artisan key:generate
to generate a new, non-mcrypt APP_KEYYou 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:
Published by snipe about 7 years ago
This pre-release contains many improvements to API consistency from the previous alphas, in addition to some smaller bugfixes and UI improvements. See the complete changelog here.
Changelog
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.
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:
.env
file: APP_CIPHER=rijndael-256
php artisan config:clear
and php artisan config:cache
php artisan cache:clear
If this fails, you CAN regenerate your app key, however this is strongly recommended against for existing installs. Changing your app key will:
If setting your APP_CIPHER
doesn't work and you have encrypted custom fields, please open a ticket instead of regenerating your app key. We'll try to work through how to resolve it without wiping your key.
Published by snipe over 7 years ago
Remember to run:
php composer.phar install --no-dev --prefer-source
php artisan config:clear
php composer.phar dump-autoload
php artisan migrate
php artisan view:clear
Published by snipe over 7 years ago
Remember to run:
php composer.phar install --no-dev --prefer-source
php artisan config:clear
php composer.phar dump-autoload
php artisan migrate
php artisan view:clear
Published by snipe over 7 years ago
bootstrap/cache/compiled.php
bootstrap/cache/services.json
php composer.phar dump-autoload
php artisan view:clear
php artisan cache:clear
php artisan config:clear
php composer.phar install --no-dev --prefer-source
php artisan migrate
You will also need to run php artisan passport:install
to initialize the new API if you have not done so already.
Big thanks to @BrettFagerlund, @steveelwood and @matc for helping us identify and fix some upgrade issues from the first 4.0-alpha. <3
Published by snipe over 7 years ago
Changelog
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.
You will also need to run php artisan passport:install
to initialize the new API.
Published by snipe over 7 years ago
Remember to run:
php composer.phar install --no-dev --prefer-source
php artisan config:clear
php composer.phar dump-autoload
php artisan migrate
php artisan view:clear
Published by snipe almost 8 years ago
Remember to run:
php composer.phar install --no-dev --prefer-source
php artisan config:clear
php composer.phar dump-autoload
php artisan migrate
php artisan view:clear