Releases: grokability/snipe-it
v4-beta4
New in v4.0-beta 4
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.
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:cacheto clear your config cache - run
php artisan snipeit:recrypter - run
php artisan key:generateto 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-beta2
New in v4.0-beta 2
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.
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:cacheto clear your config cache - run
php artisan snipeit:recrypter - run
php artisan key:generateto 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-beta3
New in v4.0-beta 3
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.
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:cacheto clear your config cache - run
php artisan snipeit:recrypter - run
php artisan key:generateto 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-beta
New in v4.0-beta
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
- FIXED #3491 - adds supplier info to assets listing
- FIXED checkout buttons on licenses list
- IMPROVED #3514 - move tinker requirement out of dev
- FIXED weird query scope that breaks stuff when querying large data
- FIXED #3514 - removed debugging code that was forcing 404
- FIXED explode for trusted proxy
- IMPROVED #3546 - increases size of field values in custom fields for listboxes
- FIXED #3556 missing group listing
- FIXED #3579 pre-flight config file warning
- FIXED #3580 - reduce minimum username size to 1
- IMPROVED #3582 - Add in location parent and child information into API requests
- ADDED Departments
- FIXED #3605 - missing table close tag causing page layout bonking
- FIXED #3602 - actions missing from suppliers in v4
- FIXED #3644 - broken datepicker
- FIXED #3651 - backups not working
- ADDED import mapper #3639
- FIXED Auto-Incrementer
- FIXED #3732 - broken tooltips and weird select2 option text behavior
- FIXED #3702 - Added artisan command to walk through special characters that were double-encoded
- ADDED Adds max thumbnail width to asset listings, settings
- FIXED #3632 and #3817 - set archived to default 0 so imported asset alerts fire
- ADDED DB port number as env variable
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
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:
- Add a line to your
.envfile:APP_CIPHER=rijndael-256 - Clear your config cache:
php artisan config:clearandphp artisan config:cache - Clear your app cache:
php artisan cache:clear - Clear your browser sessions
If this fails, you CAN regenerate your app key, however this is strongly recommended against for existing installs. Changing your app key will:
- make any encrypted fields undecryptable
- make your LDAP password undecryptable
- void all browser sessions
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.
v3.6.6
v3.6.5
New in v3.6.5
- Fixed issue with updates no longer being logged if a single item was being edited (though they were still logged if bulk editing.)
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
v4.0-alpha-2
New in v4.0-alpha-2
- Misc upgrade/migration fixes
Upgrading:
Delete:
bootstrap/cache/compiled.phpbootstrap/cache/services.json
Run:
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
v4.0-alpha
New in v4.0-alpha
Changelog
- ADDED (Experimental) Multi-field searching in asset listings
- ADDED REST API with MUCH cleaner JSON payloads
- FIXED UTF-8 issues with custom fields
- IMPROVED Upgraded to Laravel 5.4
- IMPROVED Authorization roles to de-emphasize the "admin" role and apply more granular permissions to users
- ADDED (Experimental) Ability to check assets out to users, locations and other assets
- IMPROVED Manufacturer data, adding support contact information
- ADDED Ability to customize date and time formats in Settings
- ADDED Bulk edit users for select user attributes (groups, manager, company, location)
- ADDED Ability to edit custom fields
- ADDED Support for location-specific LDAP OUs
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.
v3.6.4
New in v3.6.4
- Fixed issue that preventing searching on model number in accessories
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
v3.6.3
New in v3.6.3
- Fixed issue that preventing non-admin users with the permission to delete other users from being able to do so.
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