A free open source IT asset/license management system
AGPL-3.0 License
Bot releases are visible (Hide)
Published by snipe over 2 years ago
This release fixes a handful of bugs and improvements to Google LDAP support, the new Restore from Backup tool, and should have the latest and greatest translations strings in all languages.
created_at
time is incorrect by @inietov in https://github.com/snipe/snipe-it/pull/11133
vendor/symfony/translation/TranslatorInterface.php
in upgrader by @snipe in https://github.com/snipe/snipe-it/pull/11137
Argument 1 passed to App\Http\Requests\ItemImportRequest::import() must be an instance of App\Models\Import, null given
by @inietov in https://github.com/snipe/snipe-it/pull/11147
Full Changelog: https://github.com/snipe/snipe-it/compare/v6.0.1...v6.0.2
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.
Published by snipe over 2 years ago
Howdy all - this is just a small point release to catch a few small bugs that have surfaced since v6.0.0 launched on Friday, mostly related to LDAP instances where password syncing is enabled (specifically for first-time logins) and also the "send this user a password reset email".
We also fixed an old bug that was present in v5 and below, where we were mistakenly double-encoding custom field values in the database, and added the encrypted status of custom fields in the UI to make it easier to see which custom fields (if any) are encrypted.
Full Changelog: https://github.com/snipe/snipe-it/compare/v6.0.0...v6.0.1
Published by snipe over 2 years ago
Holy moly folks, today's the day! We're thrilled to announce the release of Snipe-IT v6.0.0. Over a year in the making, we think this is our best release yet, and although we have backported a lot of what we could to v5.4.x, there's a lot that's new and improved.
Note: Composer 2 is highly recommended for this upgrade. To upgrade your copy of composer, you can run composer self-update --2
. If you need to downgrade back to v1 at any point, you can just run composer self-update --1
.
.my.cnf
to disable column-statistics
backup for Dockerstatus_type
in StatusLabels API index endpoint [#10829]assets_count
, consumables_count
, licenses_count
, and accessories_count
on user API endpointweb.config
from Apachefile_get_contents
more gracefullyThis list looks short, and you're welcome to explore the (very long) list of changes in the autogenerated list, but they took a ton of work, both from the staff here at Grokability, and the amazing list of open source contributors who have helped make Snipe-IT even better.
We will be moving this repo from https://github.com/snipe/snipe-it to the @Grokability organization account soon. This is just a heads up for any of you that have automations that could be impacted.
We will also be changing the primary stable branch from master
to main
, shortly. Because of existing automations, we will still be pushing to master
up until Snipe-IT v7, but it will likely be about a week behind main
, so you may want to update automations there too.
If you're having trouble upgrading or you found a bug, be sure to open an issue here on Github, or pop into our Discord server. And be sure to check out our blog for Snipe-IT updates, miscellaneous tech discussions and other stuff.
{
in migration by @uberbrady in https://github.com/snipe/snipe-it/pull/11040
Full Changelog: https://github.com/snipe/snipe-it/compare/v5.4.4...v6.0.0
Published by snipe over 2 years ago
Full Changelog: https://github.com/snipe/snipe-it/compare/v6.0.0-RC-7...v6.0.0-GM
Published by snipe over 2 years ago
(This is a requirement in order for us to be able to pull forward the dependencies that will allow us to support PHP8 and beyond moving forward.)
status_id
to asset checkout API by @snipe in https://github.com/snipe/snipe-it/pull/10943
str_slug
for filename for JS export (like we do elsewhere) by @snipe in https://github.com/snipe/snipe-it/pull/10994
Full Changelog: https://github.com/snipe/snipe-it/compare/v5.4.3...v5.4.4
Published by snipe over 2 years ago
Full Changelog: https://github.com/snipe/snipe-it/compare/v5.4.2...v5.4.3
Published by snipe over 2 years ago
(This is a requirement in order for us to be able to pull forward the dependencies that will allow us to support PHP8 and beyond moving forward.)
This release fixes a few usability bugs related to table display and export, namely it fixes an issue where the export options were not being honored anymore and where HTML would appear in the exported CSV data. We also fixed an issue where hidden-by-default columns would not be remembered on page reload. (That was a nasty one to track down.)
We've also added an artisan command to log out ALL users, and improved security so that when an admin toggles a user's ability to login to OFF, it will log the user out any existing sessions they may have open.
And finally, a special congrats to @uberbrady for his first ever CVE!
Carbon\Exceptions\InvalidFormatException: DateTime::__construct(): Failed to parse time string
by @inietov in https://github.com/snipe/snipe-it/pull/10811
max_results
env value in the paginator by @snipe in https://github.com/snipe/snipe-it/pull/10797
Full Changelog: https://github.com/snipe/snipe-it/compare/v5.4.1...v5.4.2
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.
Published by snipe over 2 years ago
Thanks to our amazing community of testers, we're ready to release v6.0.0-RC-7 of Snipe-IT v6! As I mentioned in the first RC, it's a little less "sexy", since we've been back porting to v5 many of the features that the technology requirements would allow us to, but it's still exciting to see months of work finally get into people's hands.
There's not much super exciting to report other than some bug fixes and some changes from master
that got ported up to develop
- but that's kinda the point of a release candidate, right?
For those interested, we also have a development branch that introduces SCIM ("System for Cross-domain Identity Management") provisioning that we are hoping to squeeze into v6. Right now, I believe the main holdup is that the app is being quarantined, which sounds scary but just means it's not automatically hitting our endpoints after a certain time, which we need to go to the bottom of. If you're interested in the discussion in Discord, check it out here.
Please do kick the tires and let us know if you run into anything weird. Git merge can be a harsh mistress, and while we obviously test before releasing, it's certainly possible we missed something. Some of the stuff we're most interested in community feedback on is LDAP/SAML integration and S3 uploads, and the restore from backup stuff. (We do know there are a few places in the system that don't play well with S3 and/or Docker - including restoring from backups - and we're working on that, but it's not enough to stop us from releasing the golden master.)
(v6.0.0-RC-6 was bumped to v6.0.0-RC-7 because of a some JS that was automatically merged and broke the listing tables.)
Always,
Note: For consistency purposes, we'll be carrying this official v5 to v6 changelog below forward into the final release of v6.0.0 to save me the time of having to pull out save months worth of changes for each RC. :)
.my.cnf
to disable column-statistics
backup for Dockerstatus_type
in StatusLabels API index endpoint [#10829]web.config
from Apachefile_get_contents
more gracefullyFor a full list of changes, see the complete changelog. To see the details on the 300+ merged PRs to develop
since the release of v5, click here.
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php develop
.
Published by snipe over 2 years ago
Thanks to our amazing community of testers, we're ready to release v6.0.0-RC-6 of Snipe-IT v6! As I mentioned in the first RC, it's a little less "sexy", since we've been back porting to v5 many of the features that the technology requirements would allow us to, but it's still exciting to see months of work finally get into people's hands.
There's not much super exciting to report other than some bug fixes and some changes from master
that got ported up to develop
- but that's kinda the point of a release candidate, right?
For those interested, we also have a development branch that introduces SCIM ("System for Cross-domain Identity Management") provisioning that we are hoping to squeeze into v6. Right now, I believe the main holdup is that the app is being quarantined, which sounds scary but just means it's not automatically hitting our endpoints after a certain time, which we need to go to the bottom of. If you're interested in the discussion in Discord, check it out here.
Please do kick the tires and let us know if you run into anything weird. Git merge can be a harsh mistress, and while we obviously test before releasing, it's certainly possible we missed something. Some of the stuff we're most interested in community feedback on is LDAP/SAML integration and S3 uploads, and the restore from backup stuff. (We do know there are a few places in the system that don't play well with S3 and/or Docker - including restoring from backups - and we're working on that, but it's not enough to stop us from releasing the golden master.)
Always,
Note: For consistency purposes, we'll be carrying this official v5 to v6 changelog below forward into the final release of v6.0.0 to save me the time of having to pull out save months worth of changes for each RC. :)
.my.cnf
to disable column-statistics
backup for Dockerstatus_type
in StatusLabels API index endpoint [#10829]web.config
from Apachefile_get_contents
more gracefullyFor a full list of changes, see the complete changelog. To see the details on the 317 merged PRs to develop
since the release of v5, click here.
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php develop
.
Published by snipe over 2 years ago
Thanks to our amazing community of testers, we're ready to release v6.0.0-RC-5 of Snipe-IT v6! As I mentioned in the first RC, it's a little less "sexy", since we've been back porting many of the features that the technology requirements would allow us to, but it's still exciting to see months of work finally get into people's hands.
There's not much super exciting to report other than some bug fixes and some changes from master
that got ported up to develop
- but that's kinda the point of a release candidate, right?
Please do kick the tires and let us know if you run into anything weird. Git merge can be a harsh mistress, and while we obviously test before releasing, it's certainly possible we missed something. Some of the stuff we're most interested in community feedback on is LDAP/SAML integration and S3 uploads, and the restore from backup stuff. (We do know there are a few places in the system that don't play well with S3 and.or Docker - including restoring from backups - and we're working on that, but it's not enough to stop us from releasing the golden master.
Always,
Note: For consistency purposes, we'll be carrying this official v5 to v6 changelog below forward into the final release of v6.0.0 to save me the time of having to pull out save months worth of changes for each RC. :)
.my.cnf
to disable column-statistics
backup for Dockerstatus_type
in StatusLabels API index endpoint [#10829]file_get_contents
more gracefullyFor a full list of changes, see the complete changelog. To see the details on the 317 merged PRs to develop
since the release of v5, click here.
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php develop
.
Published by snipe over 2 years ago
Thanks to our amazing community of testers, we're ready to release RC-4 of Snipe-IT v6! As I mentioned in the first RC, it's a little less "sexy", since we've been back porting many of the features that the technology requirements would allow us to, but it's still exciting to see months of work finally get into people's hands.
There's not much super exciting to report other than some bug fixes and some changes from master
that got ported up to develop
- but that's kinda the point of a release candidate, right?
Please do kick the tires and let us know if you run into anything weird. Git merge can be a harsh mistress, and while we obviously test before releasing, it's certainly possible we missed something. Some of the stuff we're most interested in community feedback on is LDAP/SAML integration and S3 uploads, and the restore from backup stuff. (We do know there are a few places in the system that don't play well with S3 and.or Docker - including restoring from backups - and we're working on that, but it's not enough to stop us from releasing the golden master.
Always,
Note: For consistency purposes, we'll be carrying this official v5 to v6 changelog below forward into the final release of v6.0.0 to save me the time of having to pull out save months worth of changes for each RC. :)
.my.cnf
to disable column-statistics
backup for DockerFor a full list of changes, see the complete changelog. To see the details on the 260 merged PRs to develop
since the release of v5, click here.
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.
Published by snipe over 2 years ago
(This is a requirement in order for us to be able to pull forward the dependencies that will allow us to support PHP8 and beyond moving forward.)
This is just a point release that largely adds a few additional endpoint filters for the API.
ldap_import
, assets_count
, consumables_count
, licenses_count
and accessories_count
as filters to user API [#10773]For a full list of changes, see the complete changelog.
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.
Published by snipe over 2 years ago
(This is a requirement in order for us to be able to pull forward the dependencies that will allow us to support PHP8 and beyond moving forward.)
This is tagged as a minor release specifically because it introduces a potentially breaking change, ironically, because of something we fixed. Somewhere along the line, a few versions back, the API throttling/rate limiting functionality stopped working. We’ve corrected that behavior and now rate liming is working as expected again, which is good news overall, but if you have an integration set up that really beats up the server, you’re going to have to increase the rate limit by setting the new API_THROTTLE_PER_MINUTE
environment variable to override the default-but-generous 120 requests per minute limit. (We’ll update the docs shortly.)
We also improved (fixed?) an issue where if we didn’t specifically trap and handle an API error (404, where we tell you the endpoint isn’t found, for example) we were returning a 405 Method Not Allowed
status code, which was dumb. We still try to give you a useful error message from the API if you’re querying the wrong endpoint, etc - but we’re at least preserving the original HTTP status code, which should provide more useful debugging information. If your integration is always expecting a 405 regardless of error, you may want to revisit your code, since the API will now only return a 405 if that’s actually what’s wrong.
deleted
endpoint filter for licenses (/api/v1/licenses?deleted=true
)next_audit_date
for all assets that have a non-null next_audit_date
value.For a full list of changes, see the complete changelog.
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.
Published by snipe over 2 years ago
Thanks to our amazing community of testers, we're ready to release RC-3 of Snipe-IT v6! As I mentioned in the first RC, it's a little less "sexy", since we've been back porting many of the features that the technology requirements would allow us to, but it's still exciting to see months of work finally get into people's hands.
There's not much super exciting to report other than some bug fixes and some changes from master
that got ported up to develop
- but that's kinda the point of a release candidate, right?
Please do kick the tires and let us know if you run into anything weird. Git merge can be a harsh mistress, and while we obviously test before releasing, it's certainly possible we missed something. Some of the stuff we're most interested in community feedback on is LDAP/SAML integration and S3 uploads, and the restore from backup stuff. (We do know there are a few places in the system that don't play well with S3 and.or Docker - including restoring from backups - and we're working on that, but it's not enough to stop us from releasing the golden master.
@snipe
Note: For consistency purposes, we'll be carrying this official v5 to v6 changelog below forward into the final release of v6.0.0 to save me the time of having to pull out save months worth of changes for each RC. :)
.my.cnf
to disable column-statistics
backup for DockerFor a full list of changes, see the complete changelog. To see the details on the 260 merged PRs to develop
since the release of v5, click here.
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.
Published by snipe over 2 years ago
(This is a requirement in order for us to be able to pull forward the dependencies that will allow us to support PHP8 and beyond moving forward.)
This is a small security release that addresses possible enumeration through email addresses via the forgotten password response text, and an un-gated supplier view for an authenticated but unauthorized Snipe-IT user.
For a full list of changes, see the complete changelog.
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.
Published by snipe over 2 years ago
(This is a requirement in order for us to be able to pull forward the dependencies that will allow us to support PHP8 and beyond moving forward.)
/hardware/{id}/checkin
API response on error where it was erroneously sending a "success" message on failure$model
and $model->category
exist before return the checkin_email
propertyFor a full list of changes, see the complete changelog.
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.
Published by snipe over 2 years ago
Thanks to our amazing community of testers, we're ready to release RC-2 of Snipe-IT v6! Unlike v5's release, I think this one won't require quite so many RCs, and we're feeling pretty good about this version overall. As I mentioned in the first RC, it's a little less "sexy", since we've been back porting many of the features that the technology requirements would allow us to, but it's still exciting to see months of work finally get into people's hands.
There's not much super exciting to report other than some bug fixes and some changes from master
that got ported up to develop
- but that's kinda the point of a release candidate, right?
Please do kick the tires and let us know if you run into anything weird. Git merge can be a harsh mistress, and while we obviously test before releasing, it's certainly possible we missed something. Some of the stuff we're most interested in community feedback on is LDAP/SAML integration and S3 uploads, and the restore from backup stuff. (We do know there are a few places in the system that don't play well with S3 and.or Docker - including restoring from backups - and we're working on that, but it's not enough to stop us from releasing the golden master.
@snipe
Note: For consistency purposes, we'll be carrying this official v5 to v6 changelog below forward into the final release of v6.0.0 to save me the time of having to pull out save months worth of changes for each RC. :)
.my.cnf
to disable column-statistics
backup for DockerFor a full list of changes, see the complete changelog. To see the details on the 260 merged PRs to develop
since the release of v5, click here.
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.
Published by snipe over 2 years ago
(This is a requirement in order for us to be able to pull forward the dependencies that will allow us to support PHP8 and beyond moving forward.)
master
: Added some BS tables style overrides for better mobile UXUserAccountControl
to permitted UAC's for Active Directory.my.cnf
to disable column-statistics backupAPP_URL
unless overridenFor a full list of changes, see the complete changelog.
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.
Published by snipe almost 3 years ago
The long-awaited Release Candidate for Snipe-IT v6 is finally here! There were a lot of things that conspired against us for this to be so late (things like an ongoing global pandemic, Laravel delaying their release because of some unfortunate choices made by the PHP release managers, dependencies being trickier for the same reasons as Laravel was delayed, and so on) but here we are.
When develop
and master
start to diverge so much that it takes hours to reconcile merge conflicts, it's in everyone's best interests to push ahead with the release, even if it doesn't have every bell and whistle everyone wanted. We got a lot done for v6 - much of it is under the hood and our users won't notice (framework upgrades, security upgrades, etc), but we hope the stuff you can see will make it worth it for you. We did end up merging down a LOT of the v6 features (like G Suite Secure LDAP) back down into v5 so that you folks didn't have a wait. It makes the v6 release a little less dramatic, but we never believe in holding features back just for the sake of publicity.
As we've stated before, delays in releases for Snipe-IT don't mean the same things as they often do in other software projects, since we were still constantly releasing to the v5.x line while we were developing v6, so it's not as if nothing was moving forward and everyone was holding their breath for v6 just to see some kind of progress.
And likewise, once v6 is officially released, it doesn't mean we're not going to keep pushing forward as we always do. Like our increasing age, versions are just a number, and all the cool features we had hoped to get into v6 but couldn't will just be moved into the next version. Projects are either feature driven or date driven, they cannot be both. While we are normally feature-driven, that's because of our very fast release cycle.
We've been working on this for a long time (since about June 2021 when we broke the develop
branch off from the normal v5 bloodline). We hope you'll consider testing out the RC versions so we can make sure the rollout is as smooth as possible. As ALWAYS, do not use release candidates in production.
Note: For consistency purposes, we'll be carrying this official v5 to v6 changelog below forward into the final release of v6.0.0 to save me the time of having to pull out save months worth of changes for each RC. :)
.my.cnf
to disable column-statistics
backup for DockerFor a full list of changes, see the complete changelog. To see the details on the 260 merged PRs to develop
since the release of v5, click here.
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.
Published by snipe almost 3 years ago
(This is a requirement in order for us to be able to pull forward the dependencies that will allow us to support PHP8 and beyond moving forward.)
assets_count
on kits query, since it doesn't exist as a columnBulkAssetModelsController.php
For a full list of changes, see the complete changelog.
For general upgrading instructions, click here. Users who installed Snipe-IT via Git (recommended) can just run php upgrade.php
.