A free open source IT asset/license management system
AGPL-3.0 License
Bot releases are hidden (Show)
Published by snipe almost 4 years ago
Happy Tuesday again, friends :) Sorry for the double release today, but we discovered a conflict with the new asset counter in the sidenav and the SAML integration, since the SAML routes are loaded as a service provider. This change wouldn't affect you unless you access the SAML settings, but it's a teeny tiny update, so it's worth patching in.
Effectively, the middleware that pulls in those asset count numbers (number of deployed, etc, to inject it into the sidebar) only gets loaded on web
middleware. When using our standard routing, everything gets pulled in under that web
middleware. Since this was loaded via service provider, web
had to be explicitly stated (and wasn't), so the middleware that gets those totals wasn't being loaded, resulting in the variable the sidenav uses not ever being set. It's a small changeset, and it's always a little awkward to have to release twice in one day due to a missed error, but go ahead and get your upgrade on.
For a full list of changes, see the complete changelog.
A Note on LDAP and Okta: As many of you know, the LDAP functionality was rewritten from the ground up in version 5, and while it's been working fine for many people, we are seeing some odd throttling for folks using Okta as their LDAP provider. We're in touch with Okta now, trying to get to the bottom of it (as we're unsure if we're unintentionally beating up their API without realizing it, or if something changed on their end and it was just a crappy coincidence), but in the meantime, self-hosted folks can potentially test out this PR which reverts some of that functionality back to the v4 line. This solution isn't exactly ideal, as it means the LDAP login and LDAP sync use different methods, but if it works better for Okta customers, we'll merge that into master and re-factor it to be a little less gnarly looking.
Admin > Settings
was previously less than 8
, you should change this to 8 or greater before upgrading. Failure to update this may cause other settings to fail on saving.If you're running into an issue with images not showing up, that's due to an outdated version of upgrade.php
(outdated because of us, not you.) That script unfortunately tries (tried) to move your files to the Laravel-approved storage directory. Since that was last updated, we decided not to use that file path, so if you upgraded using upgrade.php
and your images are coming up broken, please move the files in app/storage/uploads
back to public/uploads
and remove the symlink the upgrader created for you. (After v5.0.0, the upgrader was patched to not move those files anymore, so if you skipped the v5.0.0 upgrade you should be fine and no action is needed.)
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe almost 4 years ago
Happy Tuesday, friends :) This is largely a bug fix release for some unusual use-cases that folks have been kind enough to share with us, including the dashboard pie chart, SAML integration, and LDAP syncing.
It also addresses an issue where users of some email clients (such as Gmail) would not have the images in notifications loading properly. (This is due to Gmail opting not to parse base_64
encoded images.) The attachment method has been changed to cid
, so that issue should be resolved by upgrading to this version.
For a full list of changes, see the complete changelog.
A Note on LDAP and Okta: As many of you know, the LDAP functionality was rewritten from the ground up in version 5, and while it's been working fine for many people, we are seeing some odd throttling for folks using Okta as their LDAP provider. We're in touch with Okta now, trying to get to the bottom of it (as we're unsure if we're unintentionally beating up their API without realizing it, or if something changed on their end and it was just a crappy coincidence), but in the meantime, self-hosted folks can potentially test out this PR which reverts some of that functionality back to the v4 line. This solution isn't exactly ideal, as it means the LDAP login and LDAP sync use different methods, but if it works better for Okta customers, we'll merge that into master and re-factor it to be a little less gnarly looking.
img-responsive
class to preview images for suppliers, etcAdmin > Settings
was previously less than 8
, you should change this to 8 or greater before upgrading. Failure to update this may cause other settings to fail on saving.If you're running into an issue with images not showing up, that's due to an outdated version of upgrade.php
(outdated because of us, not you.) That script unfortunately tries (tried) to move your files to the Laravel-approved storage directory. Since that was last updated, we decided not to use that file path, so if you upgraded using upgrade.php
and your images are coming up broken, please move the files in app/storage/uploads
back to public/uploads
and remove the symlink the upgrader created for you. (After v5.0.0, the upgrader was patched to not move those files anymore, so if you skipped the v5.0.0 upgrade you should be fine and no action is needed.)
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe almost 4 years ago
Happy Tuesday, everyone! This is a bug fix release that should handle a bunch of smaller UI bugs, and will hopefully help with some LDAP quirkiness you've all been kind enough to document and report for us.
Note: We did miss updating version.php
to reflect that this is from the master branch, so it may be confusing to see develop
instead of master
in your Snipe-IT footer, but this release is definitely based off the master
branch. It seemed like it would be more confusing to delete/edit the tag after it was already pushed.
last_checkout
and expected_checkin
fillable for API callsapplication/xml
in SAML upload in Safari.xlsx
file in upload. (#8386)bricelabelle/snipe-it-bulkedit
upgrade.php
script to check for PHP extensions (#8712)Admin > Settings
was previously less than 8
, you should change this to 8 or greater before upgrading. Failure to update this may cause other settings to fail on saving.If you're running into an issue with images not showing up, that's due to an outdated version of upgrade.php
(outdated because of us, not you.) That script unfortunately tries (tried) to move your files to the Laravel-approved storage directory. Since that was last updated, we decided not to use that file path, so if you upgraded using upgrade.php
and your images are coming up broken, please move the files in app/storage/uploads
back to public/uploads
and remove the symlink the upgrader created for you. (After v5.0.0, the upgrader was patched to not move those files anymore, so if you skipped the v5.0.0 upgrade you should be fine and no action is needed.)
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.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe almost 4 years ago
This is a small point release that adds a little extra functionality for extending the life of your API keys. Keys prior to this version will expire in one year, however we've added a much longer expiration for these now, which defaults to 20 years. If you'd like to override this with a shorter (or longer) expiration, add API_TOKEN_EXPIRATION_YEARS=X
(where X
is the number of years you want them to expire in) to your .env
and clear your config cache with php artisan config:cache
.
We certainly could have waited to push this out into a release later in the week, but it seemed too useful not to share it right away.
created_at
and expires_at
to Account API token UIAccount > Assigned Assets
Admin > Settings
was previously less than 8
, you should change this to 8 or greater before upgrading. Failure to update this may cause other settings to fail on saving.If you're running into an issue with images not showing up, that's due to an outdated version of upgrade.php
(outdated because of us, not you.) That script unfortunately tries (tried) to move your files to the Laravel-approved storage directory. Since that was last updated, we decided not to use that file path, so if you upgraded using upgrade.php
and your images are coming up broken, please move the files in app/storage/uploads
back to public/uploads
and remove the symlink the upgrader created for you. (After v5.0.0, the upgrader was patched to not move those files anymore, so if you skipped the v5.0.0 upgrade you should be fine and no action is needed.)
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.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe almost 4 years ago
This is a bug fix release that should handle some of the issues reported over the past week or so.
We'll be hitting them back as quickly as you can throw issues at us, so keep them coming! We appreciate it :)
all=true
to include deleted and not-deleted in one callsignature-pad.min.css
Settings > Security
option and validation to disallow password to be the same as username, email, etcAdmin > Settings
was previously less than 8
, you should change this to 8 or greater before upgrading. Failure to update this may cause other settings to fail on saving.If you're running into an issue with images not showing up, that's due to an outdated version of upgrade.php
(outdated because of us, not you.) That script unfortunately tries (tried) to move your files to the Laravel-approved storage directory. Since that was last updated, we decided not to use that file path, so if you upgraded using upgrade.php
and your images are coming up broken, please move the files in app/storage/uploads
back to public/uploads
and remove the symlink the upgrader created for you. (After v5.0.0, the upgrader was patched to not move those files anymore, so if you skipped the v5.0.0 upgrade you should be fine and no action is needed.)
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.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe almost 4 years ago
This is a bug fix release that should handle some of the issues reported over the past few days.
We'll be hitting them back as quickly as you can throw issues at us, so keep them coming! We appreciate it :)
Admin > Settings
was previously less than 8
, you should change this to 8 or greater before upgrading. Failure to update this may cause other settings to fail on saving.If you're running into an issue with images not showing up, that's due to an outdated version of upgrade.php
(outdated because of us, not you.) That script unfortunately tries (tried) to move your files to the Laravel-approved storage directory. Since that was last updated, we decided not to use that file path, so if you upgraded using upgrade.php
and your images are coming up broken, please move the files in app/storage/uploads
back to public/uploads
and remove the symlink the upgrader created for you. (After v5.0.0, the upgrader was patched to not move those files anymore, so if you skipped the v5.0.0 upgrade you should be fine and no action is needed.)
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.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe almost 4 years ago
Admin > Settings
was previously less than 8
, you should change this to 8 or greater before upgrading. Failure to update this may cause other settings to fail on saving.This is a bug fix release that should handle some of the issues reported over the past few days.
If you're running into an issue with images not showing up, that's due to an outdated version of upgrade.php
(outdated because of us, not you.) That script unfortunately tries (tried) to move your files to the Laravel-approved storage directory. Since that was last updated, we decided not to use that file path, so if you upgraded using upgrade.php
and your images are coming up broken, please move the files in app/storage/uploads
back to public/uploads
and remove the symlink the upgrader created for you. (After v5.0.0, the upgrader was patched to not move those files anymore, so if you skipped the v5.0.0 upgrade you should be fine and no action is needed.)
We'll be hitting them back as quickly as you can throw issues at us, so keep them coming! We appreciate it :)
$ldapUsers
to avoid OOM'ingFor 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.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe almost 4 years ago
Admin > Settings
was previously less than 8
, you should change this to 8 or greater before upgrading. Failure to update this may cause other settings to fail on saving.This is a bug fix release that should handle some of the issues reported over the past few days.
If you're running into an issue with images not showing up, that's due to an outdated version of upgrade.php
(outdated because of us, not you.) That script unfortunately tries (tried) to move your files to the Laravel-approved storage directory. Since that was last updated, we decided not to use that file path, so if you upgraded using upgrade.php
and your images are coming up broken, please move the files in app/storage/uploads
back to public/uploads
and remove the symlink the upgrader created for you.
We'll be hitting them back as quickly as you can throw issues at us, so keep them coming! We appreciate it :)
ad_append_domain_help
stringFor 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.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe almost 4 years ago
Admin > Settings
was previously less than 8
, you should change this to 8 or greater before upgrading. Failure to update this may cause other settings to fail on saving.This is a bug fix release that should handle some of the issues reported over the past few days. While it's a little gauche to have another release out so soon after the big one, we also expect some bugs, and we're grateful for everyone's thoughtful bug reports. We tested v5 quite a lot, but it was a pretty big update, so we knew there would be some issues - and this probably won't be the last point release that happens this week.
If you're running into an issue with images not showing up, that's due to an outdated version of upgrade.php
(outdated because of us, not you.) That script unfortunately tries (tried) to move your files to the Laravel-approved storage directory. Since that was last updated, we decided not to use that file path, so if you upgraded using upgrade.php
and your images are coming up broken, please move the files in app/storage/uploads
back to public/uploads
and remove the symlink the upgrader created for you.
We'll be hitting them back as quickly as you can throw issues at us, so keep them coming! We appreciate it :)
upgrade.php
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.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe almost 4 years ago
Admin > Settings
was previously less than 8
, you should update this to 8 or greater before upgrading. Failure to update this may cause other settings to fail on saving.It's finally here!
The long-awaited v5 of Snipe-IT is finally here. I'm probably missing some of the new features and fixes in this changelog, but I'm doing my best to recount the past two years of work here.
We've rewritten the LDAP/AD functionality from the ground up, which will hopefully make those integrations a little less painful. We've also gone through several framework upgrades (sometimes because we wanted that functionality and sometimes because there were security updates that we just had to upgrade to whether we wanted to or not.)
The small things matter as much to us as the big ones do, so we've spent some time trying to really refine some of the commonly used UI elements, for example the improved logo upload+preview interface:
We've also added the ability to add multiple new assets at once from the create asset interface:
Now that master
and develop
are back at parity (and boy, it's been a while for that), expect our normal fever-pitch velocity to be back with gusto. There are still so many things we have on deck - new features, improvements, and even new products. We thank you all so much for your patience and support. <3
Note: S3 functionality for file storage is still in beta. We had hoped to launch v5 with that fully working, but we realized that not that many of our users care that deeply about it, and it would only delay us further. We'll be tweaking and tuning that functionality over the next month or two tho.
Another Note: Our beta versions of "kits" allowed for accessories and license, etc - we discovered a bug where while non-assets are checked out, they don't get recorded in history if the quantity is greater than one, so we've pulled those options for now. Once we have a chance to correct that bug, we'll be adding licenses, accessories, etc back into the new Kit feature.
upgrade.php
next_audit_date
if none providedsamaccountname
on LDAP importFor 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.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe about 4 years ago
This is the golden master for Snipe-IT v5. Primary in this release are some critical fixes for AD login.
Awesome! First things first, you should NOT test this in production yet, as it's a beta release. If you'd like to help us test, make a new copy of Snipe-IT and upgrade your copy to v5.0.0-beta-4.0, that way your data is safe. You should treat this test instance as a version you could easily throw away when you're done testing. (Hopefully it won't come to that, but hey, computers are hard.)
Things we're very interested in folks testing:
If you need to create new bug reports for this beta release, please make sure you include the beta release version in the Github issue title so we can easily see that it's an issue specific to this beta.
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.
Please see the upgrade instructions here. After completing the upgrade below, be sure to clear your browser cookies.
Published by snipe about 4 years ago
This is the golden master for Snipe-IT v5. Primary in this release are some critical fixes for AD interoperability.
ldap_host
, and improve OU handlingAwesome! First things first, you should NOT test this in production yet, as it's a beta release. If you'd like to help us test, make a new copy of Snipe-IT and upgrade your copy to v5.0.0-beta-4.0, that way your data is safe. You should treat this test instance as a version you could easily throw away when you're done testing. (Hopefully it won't come to that, but hey, computers are hard.)
Things we're very interested in folks testing:
If you need to create new bug reports for this beta release, please make sure you include the beta release version in the Github issue title so we can easily see that it's an issue specific to this beta.
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.
Please see the upgrade instructions here. After completing the upgrade below, be sure to clear your browser cookies.
Published by snipe about 4 years ago
This newest release candidate is largely UI tweaks and polish.
Awesome! First things first, you should NOT test this in production yet, as it's a beta release. If you'd like to help us test, make a new copy of Snipe-IT and upgrade your copy to v5.0.0-beta-4.0, that way your data is safe. You should treat this test instance as a version you could easily throw away when you're done testing. (Hopefully it won't come to that, but hey, computers are hard.)
Things we're very interested in folks testing:
If you need to create new bug reports for this beta release, please make sure you include the beta release version in the Github issue title so we can easily see that it's an issue specific to this beta.
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.
Please see the upgrade instructions here. After completing the upgrade below, be sure to clear your browser cookies.
Published by snipe about 4 years ago
This is a bug fix release that handles some LDAP paging issues and adds some additional fields into the importer.
firstinitial.lastname
, lastname_firstinitial
, firstnamelastname
and firstnamelastinitial
to username formatsldap_control_paged_result()
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.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe about 4 years ago
has_eula
to categoriescheckin_email
to category listing[object object]
in companies date displaysAwesome! First things first, you should NOT test this in production yet, as it's a beta release. If you'd like to help us test, make a new copy of Snipe-IT and upgrade your copy to v5.0.0-beta-4.0, that way your data is safe. You should treat this test instance as a version you could easily throw away when you're done testing. (Hopefully it won't come to that, but hey, computers are hard.)
Things we're very interested in folks testing:
If you need to create new bug reports for this beta release, please make sure you include the beta release version in the Github issue title so we can easily see that it's an issue specific to this beta.
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.
Please see the upgrade instructions here. After completing the upgrade below, be sure to clear your browser cookies.
Published by snipe about 4 years ago
Awesome! First things first, you should NOT test this in production yet, as it's a beta release. If you'd like to help us test, make a new copy of Snipe-IT and upgrade your copy to v5.0.0-beta-3.0, that way your data is safe. You should treat this test instance as a version you could easily throw away when you're done testing. (Hopefully it won't come to that, but hey, computers are hard.)
Things we're very interested in folks testing:
If you need to create new bug reports for this beta release, please make sure you include the beta release version in the Github issue title so we can easily see that it's an issue specific to this beta.
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.
Please see the upgrade instructions here. After completing the upgrade below, be sure to clear your browser cookies.
Published by snipe over 4 years ago
This is a bug fix release that handles an issue with the Select2 dropdown that would cause them to stop loading additional items in some circumstances. Additionally, we've consolidated the security headers into one middleware file, fixed a display bug on column selectors that used an icon, and created a few additional command line tools that we hope will be helpful to folks.
scopeDueOrOverdueForAudit()
location_id
to rtd_location_id
in the API on asset creation when the asset is not assigned. (This mirrors the GUI behavior)Strict-Transport-Security
headerFor 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.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe over 4 years ago
sr-only
tags and labels for accessibilityFor 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.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe over 4 years ago
This is a small bug fix release that handles a minor style regression from the previous version, and addresses an issue where the admin settings would not save (and would provide no useful error) if Slack settings were incomplete.
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.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.
Published by snipe over 4 years ago
This release brings a ton of accessibility fixes, a set of new dark-mode skins (and a new high-contrast skin), a few bug fixes, and a few UI improvements.
To use these new skins, go to Admin Settings > Branding and select them from the dropdown.
compact($id)
errors when an asset/license/location/etc was not foundnpm run prod
composer.phar
on upgrade (if it's being used)rtd_location_id
to API searchFor 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.
After completing the upgrade process, be sure to clear your browser cookies.
Please see the upgrade instructions here.