Skip to content

Releases: snipe/snipe-it

v6.3.4

29 Mar 13:40
Compare
Choose a tag to compare

Caution

The upcoming v7 release of Snipe-IT will require PHP 8.1 or greater

Happy Friday! Lots of fixes and improvements in this version. Here's the tldr;, with the full changelog below:

  • Added Somali translation
  • Fixed several label setting glitches
  • Fixed some API scoping issues where results were not as constrained as they should have been when searching
  • Added column selectors and signatures to the "print all assigned" page
  • Added 2FA reset logging (this shows up as a separate action, not a normal user edit)
  • Added AVIF as an accepted image format
  • Added ability to "toggle all" columns in the list views on most pages
  • Added the ability to "deep link" to search results in those list views
  • Updated the documentation to reflect that the php exif library is required

Warning

Upcoming Breaking API change! In between the last release and this one, we also discovered that a change we made midway through releases broke the Jamf2Snipe integration for adding/updating assets. We had changed the "shape" of the asset response to be more consistent with how we present that JSON in other API responses - however in doing so, we broke some of the Jamf2Snipe capabilities. We've reverted that change for now, but in the next release, we'll be adding that change back and updating the Jamf2Snipe library to match that capability.

We are noticing in some of the translations in CrowdIn that some trans_choice() translations are showing with a weird <unk> symbol instead of the pipe (|) symbol that the translations strings need in order to decide whether or not to pluralize a string. We've been fixing them as we find them, but if you see anything unusual, open an issue here or propose the change in our CrowdIn project.

What's Changed

New Contributors

Full Changelog: v6.3.3...v6.3.4

v6.3.3

08 Mar 10:08
Compare
Choose a tag to compare

Warning

Future versions of Snipe-IT will require PHP 8.1 or greater

This is a small patch release that fixes a few regressions introduced in the last released related to labels. It also includes some minor security patches, and introduces a new script to convert a previously unencrypted custom field to be an encrypted custom field.

v7 is still well on its way. We hit a small snag with Laravel's switch from Swiftmailer to Symfony for mail sending, but we're back on track now.

What's Changed

New Contributors

Full Changelog: v6.3.2...v6.3.3

v6.3.2

05 Mar 19:09
Compare
Choose a tag to compare

⚠️ IMPORTANT: Future versions of Snipe-IT will require PHP 8.1 or greater

What's Changed

Full Changelog: v6.3.1...v6.3.2

v6.3.1

15 Feb 14:52
Compare
Choose a tag to compare

⚠️ IMPORTANT: Future versions of Snipe-IT will require PHP 8.1 or greater

What's Changed

New Contributors

Full Changelog: v6.3.0...v6.3.1

v6.3.0

27 Jan 15:35
Compare
Choose a tag to compare

⚠️ IMPORTANT: Future versions of Snipe-IT will require PHP 8.1 or greater

Happy New Year, everyone! This update is a big one as we ramp up for the release of v7. We've got tons of bug-fixes, big and small, and we're stoked to announce support for Microsoft Teams in the notification integrations. As we continue work on v7, expect even more improvements and flexibility in notifications down the line.

We've also added the ability to specify custom fields that you would like to appear on the requestable assets page, and added user edit logging to track changes to users in the system (minus passwords, 2fa tokens, etc, of course), along with some bulk editing, LDAP and SAML improvements.

The full list of changes is below - enjoy!

What's Changed

Read more

v6.2.3

16 Oct 19:23
Compare
Choose a tag to compare

⚠️ IMPORTANT: Future versions of Snipe-IT will require PHP 8.1 or greater

This release is largely a bug fix release. There were some rare conditions where asset history wouldn't show because the original item (location, etc) were both soft-deleted and then purged, which was causing a 500 error. This didn't affect most users, but for the ones it did affect, this was an important fix.

This also fixes a migration issue between older versions of Snipe-IT upgrading to newer versions where it would have issues with the eol_explicit field, since the asset observer tries to modify that field, but it didn't necessarily exist yet depending on where you were at with migrations. This issue is now resolved.

What's Changed

  • Added tighter controls for matching log ID and item_id by @snipe in #13726
  • Set resend acceptance to POST by @snipe in #13727
  • Fixes qty remaining requirements for component checkout via API by @snipe in #13728
  • Fixed the storing of group permissions when creating via API by @marcusmoore in #13734
  • Fixed notification logic to ensure check in and out emails are delivered by @marcusmoore in #13733
  • Resolves issue with migrations with table prefixes by @spencerrlongg in #13745
  • Fixed #13723 - race condition on asset observer for older migration by @snipe in #13748
  • Handle case where value is deleted in history by @snipe in #13749

Full Changelog: v6.2.2...v6.2.3

v6.2.2

06 Oct 19:20
Compare
Choose a tag to compare

⚠️ IMPORTANT: Future versions of Snipe-IT will require PHP 8.1 or greater

This is largely a bug fix and a security release, with an XSS bug reported shahzaibak96 on Huntr.Dev that would allow potential XSS attacks to be executed in the "Changed" column as the names of things that were old/new were not being properly escaped. We encourage folks to upgrade.

What's Changed

Full Changelog: v6.2.1...v6.2.2

v6.2.1

02 Oct 13:49
Compare
Choose a tag to compare

⚠️ IMPORTANT: Future versions of Snipe-IT will require PHP 8.1 or greater

Oh hai there! v6.2.1 of Snipe-IT fixes a weird but important bug where if you had ANY encrypted custom fields, the asset history would show the changed values as encrypted, even if that specific field wasn't. We also did some polishing up of some of the UI elements, adding a copy icon next to license product keys and assets serials. (Let us know if you want that added elsewhere - those two seemed like a good start.) We also resolved a small usability bugaboo where when you'd click on the "new" icon, the name field (generally the first field in the modal) now takes the focus, which means you can start typing without having to click into the name field.

We've also improved the UI of the "Integrations" setting, where you can no longer add a non-URL ("test", for example) and save those settings. For the full details, see the changelog below!

We're going to double-down on focusing on Snipe-IT v7, so expect things to be a little quiet for a bit and then very, very loud. Snipe-IT v7 will require at least PHP v8.1 (and will support PHP v8.2+) and will clear the path for cool stuff like customizable action hooks, custom fields on more than just assets, and a bunch of other neat features.

Reminder that Snipe-IT v7 WILL REQUIRE PHP 8.1 or higher!! This is a slightly higher version than the PHP 8.0 version we've been saying for a while now, so please make sure you're ready.

We did have to comment out the new feature we were SO excited about - draggable columns. Nobody is sadder about that than we are, but in some circumstances, dragging a column would result in the data in that column being mismatched, so we had to make the very difficult call to pull the feature for now. We're still working on it, and we know how important a feature it is to many of you, but we have to make sure it's bulletproof this next time.

What's Changed

Full Changelog: v6.2.0...v6.2.1

v6.2.0

25 Sep 10:20
Compare
Choose a tag to compare

⚠️ IMPORTANT: Future versions of Snipe-IT will require PHP 8.1 or greater

Welcome to the release notes for Snipe-IT 6.2. We've been trying to fix as many bugs (and sneak in as many small features) as we can before Snipe-IT v7 comes out.

Reminder that Snipe-IT v7 WILL REQUIRE PHP 8.1 or higher!! This is a slightly higher version than the PHP 8.0 version we've been saying for a while now, so please make sure you're ready. The reason for this slight bump in minimum requirements is that we've decided to launch Snipe-IT v7 on Laravel 10, which requires that slightly higher version. Our goal is to have Snipe-IT v7 out in a month or two.

Highlights

This release includes lots of bug fixes detailed below. It introduces a new label engine which will hopefully be a big help to those folks who have struggled with getting their specific printers to work with Snipe-IT labels, but also has a legacy fallback, so if you have things just right, nothing needs to change for now.

We've also added back the sticky header for long lists, and column-reordering in those table views:

Screen.Recording.2023-09-15.at.10.04.46.PM.mov

Additionally, we made some improvements to the importer, added a minimum quantity on models so you will get those alerts in your bell icon when you don't have enough of a particular asset model available. And we've fixed a few small inconsistencies in the API with regards to boolean fields.

Important! SCIM support did not previously support changing email addresses via Azure and some other SCIM clients. Under v6.2, that has been fixed, but if you were depending on the previous behavior, you may get unexpected results.

What's Changed

Read more

v6.1.2

05 Jul 13:43
Compare
Choose a tag to compare

⚠️ IMPORTANT: Future versions of Snipe-IT will require PHP8.1 or greater

What's Changed

This is a small point release that fixes some bugs and handles some SCIM debugging a little better.

What's Changed

Full Changelog: v6.1.1...v6.1.2