Skip to content

Releases: grokability/snipe-it

Release list

v8.6.3

v8.6.3 Latest
Latest

Choose a tag to compare

View all tags
@snipe snipe released this 15 Jun 21:24
v8.6.3
cfd1ff8

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater, 8.4+ recommended. PHP 8.2 is still in security release support until 31 Dec 2026, but let's not play that game

This is largely a security release, but also fixes some more niche SCIM/LDAP issues and adds some additional UX love around more confusing and/or dangerous features (such as remote login headers.)

What's Changed

  • Authentication/LDAP - Fixed [FD-56031] - throw Exception if STARTTLS fails by @uberbrady in #19190

Full Changelog: v8.6.2...v8.6.3

Contributors

uberbrady
Assets 2
Loading

v8.6.2

v8.6.2

Choose a tag to compare

View all tags
@snipe snipe released this 13 Jun 19:33
v8.6.2
3680198

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater, 8.4+ recommended. PHP 8.2 is still in security release support until 31 Dec 2026, but let's not play that game

aa-aaa

Happy Caturday, nerds!

This release largely addresses some SCIM issues stemming from the newly mappable fields from the last release (largely affecting Azure/Entra and Okta, since they both behave very differently), and a handful of security issues and general bugs, but we also added new markdown textarea custom fields.

We've also optimized a bunch of queries to speed custom asset report and the models API endpoint.

BUT ALSO - there's one new feature that we're excited about that may or may not matter to your workflow:

Feature: "Floater" company setting

We've always had two use cases for FMCS: folks who wanted null to be a sort of floater company where anything can be assigned to users without a company, and people who wanted null company to act as a pseudo company, where it was restricted to only fellow-null-company-ed things.

We now have a setting in Admin Settings > General > Treat items and users without company associations as floaters.

When disabled, items can only be checked out to targets without a company association if the item also has no company - null is treated as its own pseudo-company. When enabled, items from any company can be checked out to targets with no company assignment.

New QR Codes for Non-Assets

We also now include QR codes for things-other-than-assets (locations, etc). Those will generally show up in your side info-panel. They are not customizable at this point, they just serve as a simple way to, for example, scan the QR code on your phone from your laptop to continue your work on a mobile device. I'm sure we'll get tons of feedback on how people want those to work moving forward and we'll adjust accordingly.

SCIM Fixes

A lot of these fixes address Azure/Entra specifically, but we've improved support for managers, email addresses, user work addresses and groups.

Documentation

We're (still, always) working as quickly as we can to update the docs with new endpoints, new screenshots, all the new features, etc. We appreciate your patience. We're pretty proud of the work that's gone into our docs, but that also means every release means a bunch of places that need updates. We're working on it as fast as we can, but if there's something that isn't documented or you have a question about in the meantime, our GH Discussions or Discord are a great place to start.

Security

There are (as always) security improvements, so folks are encouraged to upgrade, even if none of the stuff we're excited about is stuff you're excited about.

What's Changed

Full Changelog: v8.6.1...v8.6.2

Contributors

uberbrady, snipe, and 2 other contributors
Loading

v8.6.1

v8.6.1

Choose a tag to compare

View all tags
@snipe snipe released this 27 May 08:44
v8.6.1
4d06e81

This is a re-tag because we suspect one of the merges for multiple companies got mushed up, so the feature list will be the same as the v8.6.0 release. We repeated the feature list here since a lot of folks (understandably) don't watch the releases that closely and we didn't want them to miss the good stuff!

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater, 8.4+ recommended. PHP 8.2 is still in security release support until 31 Dec 2026, but let's not play that game

Wow wow wow. Wow.

We know it was just two weeks ago from our last mid-release, but this one was just too juicy to sit on. The changelog looks small, but it addresses some of our most sought-after features. Here's the highlight reel:

Users can now have more than one company

Yep. If you have FMCS (Full Multiple Company Support) enabled and need to control access via companies, this was previously potentially a problem. You might have a user who you don't want to promote to superuser (the only permission that bypasses FMCS constraints, but also has a LOT of access to stuff you might not want them to have), but they needed to manage items across several companies, and we couldn't support that in the past. Now we do.

Screenshot 2026-05-20 at 6 54 12 PM Screenshot 2026-05-20 at 6 53 50 PM Screenshot 2026-05-20 at 6 53 01 PM Screenshot 2026-05-20 at 6 48 47 PM Screenshot 2026-05-20 at 6 57 09 PM

Bulk license seat checkin via GUI

Screen.Recording.2026-05-22.at.11.32.35.AM.mov

Bulk checkin assets via GUI

Screen.Recording.2026-05-21.at.10.08.14.PM.mov

SCIM

We've ironed out a bunch of provider-specific SCIM issues that came from us adding groups, locations, manager, and company, but we are still hearing small murmurs about Okta SCIM integration, so if you're having trouble, do let us know.

Also, the new multiple-companies-for-users isn't supported by SCIM (yet?), so we suggest waiting on mapping groups if you have a situation where users might belong to multiple companies. (That mapping gets squirrely with different providers - we're working through issues as quickly as we can.)

Reddit? Somehow?

So there was an unofficial (but blessed by us) subreddit for Snipe-IT. The creator of the sub asked for a mod to take it over, and we applied and - oh no - we were approved, because we needed one more place to keep track of bugs and requests. Anyway, if Reddit is your jam, you can find us here: https://www.reddit.com/r/Snipe_IT/ - Don't be super-shocked if we direct you back to GH if your ask is a bug or a feature request though.

Documentation

This is our second release in a month, and a lot has changed. We're working as quickly as we can to update the docs with new endpoints, new screenshots, all the new features, etc. We appreciate your patience. We're pretty proud of the work that's gone into our docs, but that also means every release means a bunch of places that need updates. We're working on it as fast as we can, but if there's something that isn't documented or you have a question about in the meantime, our GH Discussions or Discord are a great place to start,

Security

There are (as always) security improvements, so folks are encouraged to upgrade, even if none of the stuff we're excited about is stuff you're excited about.

Mobile Update

We're slated to release the official Snipe-IT mobile app this week! And of course it will be open source. It will be a beta release, so be kind - a lot of work has gone into this over the past year, and we're pretty proud of what we've got (but we also know that this is the beginning, not the end, of the task.)

API pagination

If you use our API, we've simplified the pagination parts. Before, if you were building an integration, you'd have to do a bunch of math (booo) to figure out what the limit and offset were. We've made this a lot simpler for you, so you can now pass page=1, page=2, and we'll sort it out for you. You can still use the old offset/limit parameters, so nothing needs to change on your end if you've already got something that works, but new integrations should be a bit easier now.

What's Changed

Join the Community!

Full Changelog: v8.5.0...v8.6.1

Contributors

joelpittet, snipe, and 2 other contributors
Loading

v8.6.0

v8.6.0

Choose a tag to compare

View all tags
@snipe snipe released this 26 May 23:35
v8.6.0
c02a6c1

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater, 8.4+ recommended. PHP 8.2 is still in security release support until 31 Dec 2026, but let's not play that game

Wow wow wow. Wow.

We know it was just two weeks ago from our last mid-release, but this one was just too juicy to sit on. The changelog looks small, but it addresses some of our most sought-after features. Here's the highlight reel:

Users can now have more than one company

Yep. If you have FMCS (Full Multiple Company Support) enabled and need to control access via companies, this was previously potentially a problem. You might have a user who you don't want to promote to superuser (the only permission that bypasses FMCS constraints, but also has a LOT of access to stuff you might not want them to have), but they needed to manage items across several companies, and we couldn't support that in the past. Now we do.

Screenshot 2026-05-20 at 6 54 12 PM Screenshot 2026-05-20 at 6 53 50 PM Screenshot 2026-05-20 at 6 53 01 PM Screenshot 2026-05-20 at 6 48 47 PM Screenshot 2026-05-20 at 6 57 09 PM

Bulk license seat checkin via GUI

Screen.Recording.2026-05-22.at.11.32.35.AM.mov

Bulk checkin assets via GUI

Screen.Recording.2026-05-21.at.10.08.14.PM.mov

SCIM

We've ironed out a bunch of provider-specific SCIM issues that came from us adding groups, locations, manager, and company, but we are still hearing small murmurs about Okta SCIM integration, so if you're having trouble, do let us know.

Also, the new multiple-companies-for-users isn't supported by SCIM (yet?), so we suggest waiting on mapping groups if you have a situation where users might belong to multiple companies. (That mapping gets squirrely with different providers - we're working through issues as quickly as we can.)

Reddit? Somehow?

So there was an unofficial (but blessed by us) subreddit for Snipe-IT. The creator of the sub asked for a mod to take it over, and we applied and - oh no - we were approved, because we needed one more place to keep track of bugs and requests. Anyway, if Reddit is your jam, you can find us here: https://www.reddit.com/r/Snipe_IT/ - Don't be super-shocked if we direct you back to GH if your ask is a bug or a feature request though.

Documentation

This is our second release in a month, and a lot has changed. We're working as quickly as we can to update the docs with new endpoints, new screenshots, all the new features, etc. We appreciate your patience. We're pretty proud of the work that's gone into our docs, but that also means every release means a bunch of places that need updates. We're working on it as fast as we can, but if there's something that isn't documented or you have a question about in the meantime, our GH Discussions or Discord are a great place to start,

Security

There are (as always) security improvements, so folks are encouraged to upgrade, even if none of the stuff we're excited about is stuff you're excited about.

Mobile Update

We're slated to release the official Snipe-IT mobile app this week! And of course it will be open source. It will be a beta release, so be kind - a lot of work has gone into this over the past year, and we're pretty proud of what we've got (but we also know that this is the beginning, not the end, of the task.)

API pagination

If you use our API, we've simplified the pagination parts. Before, if you were building an integration, you'd have to do a bunch of math (booo) to figure out what the limit and offset were. We've made this a lot simpler for you, so you can now pass page=1, page=2, and we'll sort it out for you. You can still use the old offset/limit parameters, so nothing needs to change on your end if you've already got something that works, but new integrations should be a bit easier now.

What's Changed

Join the Community!

Full Changelog: v8.5.0...v8.6.0

Contributors

joelpittet, snipe, and 2 other contributors
Loading

v8.5.0

v8.5.0

Choose a tag to compare

View all tags
@snipe snipe released this 12 May 20:39
v8.5.0
90c8689

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater, 8.4+ recommended. PHP 8.2 is still in security release support until 31 Dec 2026, but let's not play that game

We're SO stoked to release v8.5 of Snipe-IT for so many reasons!

Tons of bug fixes, and also - we now support PHP 8.5! We're also now on Laravel 12, which won't matter to most folks, but means we can start to move forward on some really cool stuff that the framework limitation kept us from doing.

As always, the nitty gritty is in the What's Changed below - but very importantly, this release addresses several security issues, so we strongly encourage everyone to update as soon as is feasible.

BUT FIRST - The Snipe-IT Mobile App

Everyone wants to know about the mobile app. We're freakishly close to a beta release. So much progress has been made already, the suspense is killing us. We were hoping to time this release with more specific news about the mobile app, but this release means that when the mobile app does launch, it will be a much better experience. Watch this space - it's happening soon.

Complex Advanced Search Queries

We've heard from so many people about how the "advanced" search wasn't so... advanced.

Previously, the advanced search (the icon with the + sign in it) was... okay. We've supercharged it in this release to allow and vs or, and also some pretty cool add-ons to be able to filter in a much more nuanced way.

Screenshot 2026-05-12 at 7 57 19 PM

Advanced searches return a partial match by default. For more specific results, you can use not:value to fuzzy-exclude, is:value for an exact match, is_not:value for an exact exclusion, is:null for empty values, and is:not_null for non-empty. (In these examples, value is the text you are searching for - or seeking to exclude.)

This is all API-powered, so if you're using the API in a more complicated way, you automatically have all of this new operator and filter functionality. (We're a little behind on the docs, but we'll have that updated soon, I swear.)

Small usability issue - hitting enter (or return) on that advanced search modal will now submit the form.

Let's Talk About SCIM, Baby

SCIM now officially supports groups, location, company, and manager syncing. Because of how SCIM works, this won't happen automagically, you'll need to map those fields in your directory service provider, and we'll have updated docs for that shortly.

This is a shockingly short blurb about stuff that took a really long time, but for the folks who cared about this in the first place, it's a big deal.

Caution

If you have internal groups that are named the same as Snipe-IT permission groups, you could accidentally overwrite permission groups in Snipe-IT. Use this carefully, and definitely make a backup first.

Bulk Delete Licenses

While this shouldn't come up too often, imports do go bad and providers change sometimes. If you have a bunch of licenses that have no seats assigned, you can now delete them in bulk.

Screen.Recording.2026-05-12.at.1.10.36.PM.mov

Re-Send Asset Acceptance from the user view

You can now re-send the unaccepted item notice from a user's page (if they have outstanding items that have not been signed for or the EULAs were not yet accepted.)

Screenshot 2026-04-16 at 3 57 00 PM

Sign in Place

SO many people have asked for this, and we're so jazzed to be able to release it. If your workflow requires a user to sign in place - as in they are literally standing there - you can do that now. It will still direct you to your intended destination after the user accepts what's been assigned, but you can now do that in-place, in-person.

Screenshot 2026-04-14 at 9 23 22 PM

That checkbox will remember your previous choice, so for folks who really wanted this to streamline their workflow, this should help a lot. (Admittedly not our best work in terms of test data screenshots.)

Report Dashboard

Reports have always been a weird outlier in terms of information architecture here. We've made some big improvements in that department, so anyone with reports permission will now see this:

Screen.Recording.2026-05-11.at.2.24.58.PM.mov

Custom Asset Report

You can now use "only assigned" or "only unassigned" in the custom asset report.

AI Stuff

While it's not in this release, we are working on a built-in MCP server, so if AI is your thing, stay tuned.

What's Changed

Read more

Contributors

uberbrady, snipe, and 7 other contributors
Loading

v8.4.1

v8.4.1

Choose a tag to compare

View all tags
@snipe snipe released this 07 Apr 20:47
v8.4.1
8802615

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater, 8.3+ recommended.

Happy Tuesday! This release introduces an updated UI, improved searching, and fixes several security issues. All users are encouraged to upgrade.

A lot of what we've been working on has been under the hood - code improvements to make it easier for us to more quickly and reliably act on things you folks have been asking for. They don't look like a lot on the face, but they're important to get the project to a state where we can move a bit faster.

As such, you will definitely want to run php artisan view:clear to clear your old cached views. If you're using the upgrade.php script, it will do that for you, so no need to worry about it.

UI Changes

As you'll notice, we did switch up the UI on detail pages a bit. We've introduced a new component that we're calling the "info panel".

Screen.Recording.2026-03-20.at.5.42.43.PM.mov

It might be a little confusing to start with, but we think you're really going to like it. For all "first class objects", all of the most common information will now be available consistently, in the same place, every time.

The new info panel includes copy-to-clipboard functionality for just about everything, and if you don't need that information and want to work with the wider table view, just click on the arrow button to hide it. The show/hide is stored in local storage, so it will remember whether you wanted it open or not as you navigate through the system. The hover tooltips will give you more information when it's available or necessary.

We've tried to listen to feedback about the most important elements that people care about when they are viewing an item's detail page and give those priority. We know change is hard though, so keep that feedback coming. We can't promise we can act on every piece of feedback we get, but we listen to all of it and ultimately are committed to making your experience with the product as good as it can be.

At the end of the day, any time you change the UI on anything, people will have Big Feelings. Some of the feedback we've gotten so far is really positive, some less so - but we're always listening, even if you fall on the "less so" side of things.

We've also introduced some mobile navigation improvements, turning the tabbed interface into a dropdown on very small screens.

Uploads for Departments and Companies

You can now add files to departments and companies, if that's the sort of thing you're into.

A quick mea culpa to our hosted customers

In the process of migrating some of you to newer, faster machines, some of you were upgraded a little earlier than we had planned, while things weren't quite polished up. Many of you have reached out via the helpdesk and we've gotten you sorted, but we're sorry that happened. We would have at least wanted to give you a heads up about the UI changes.

We always want the hosted experience to be the most excellent way to use Snipe-IT, and this past week was a little rockier for some of you. We're taking steps to make sure that doesn't happen again when we need to migrate customers from one server to another.

What's Next

We have an upgrade to Laravel 12 sitting on develop which will fully support PHP 8.5, and very shortly after that, group support for SCIM.

Potentially Breaking Changes

The filters for asset status type, (Pending, RTD, Archived, Deleted, etc) have been changed from status=Archived to status_type=Archived.

Documentation Platform Bugs

Our current documentation platform is having some issues and some pages might not be available. After many hours talking to their support (and their stupid AI chatbot), we're going to have to revert some of the formatting on many of the pages to get them to render. How did this happen? No idea. We didn't change anything. But we need to get those pages back online for you and new folks who want to install Snipe-IT. If you get an error in the docs saying that the page cannot be rendered, just open a GH issue and we'll jump right on that. We have a lot of docs to get through, and we're starting with the most common pages first.

Mobile App Update

We've created a Google Form so we can start tracking people who want in on the Testflight invite. Please fill in this form if you're interested in helping us test! https://forms.gle/HEsWuHSqLLjx8xnR8.

What's Changed

Read more

Contributors

uberbrady, joelpittet, and 9 other contributors
Loading

v8.4.0

v8.4.0

Choose a tag to compare

View all tags
@snipe snipe released this 23 Feb 20:59
v8.4.0
8d0fda8

Happy Monday! Today we're releasing 8.4.0 of Snipe-IT! In it you'll find tons of small bug fixes and some bigger ones.

As always, we highly recommend upgrading to the latest stable version of Snipe-IT, as we are constantly improving the product and patching security issues we come across.

Smallish:

  • Several small security fixes
  • Loads of fixes to light/dark mode
  • Some label scaling fixes
  • Less noisy SCIM debugging when it's not actually helpful
  • Ability to clone components
  • Fixed a few breadcrumb titles

Biggish?

  • We identified a few queries that were not optimized as well as they could be, so it was creating an "n+1" problem. The more items you had, the more queries you'd be doing. We've fixed those and things should be a LOT snappier now.
  • We've added sticky columns to most of the table views. We have tried really hard to make them be the ones that make sense (name, as the left-side sticky, and actions and/or checkin/checkin where appropriate). I expect you'll let us know if we guessed wrong here.
  • A more standardized right-side panel in most screens (not users and not assets or "Your Profile" yet). We're really quite excited about this, as we feel it exposes a lot more of the potentially important information you need to see while looking at an item than we we used to. A few fewer clicks, and a lot more information exposed, but also able to be tucked away if you need larger screen real-estate.

What's Changed

Read more

Contributors

uberbrady, joelpittet, and 13 other contributors
Loading

v8.3.7

v8.3.7

Choose a tag to compare

View all tags
@snipe snipe released this 12 Dec 09:13
v8.3.7
78d1256

Happy Friday!

As always, we highly recommend upgrading to the latest stable version of Snipe-IT, as we are constantly improving the product and patching security issues we come across.

This release looks small, but it introduces a much cleaner, MUCH faster dark/light scheme that we're really excited about, the ability to download imported CSVs from the import screen, some restore and import improvements, and a bunch of improvements to labels.

To clarify the way the new dark/light mode works, here are a few key points (also see the videos in #18249 for more visual details):

We used to have a set of predefined skins, a collection of colors, with light and dark modes, and they were okay, but they often fell out of sync with UI changes resulting in inconsistent results between light and dark skins. Those are gone now.

We now use your selected header color (if you have one) from Admin Settings > Branding and your light mode/dark mode settings and make the UI colors feel more like you. Changing from dark mode to light mode is now just a menu click away, and if you don't have any preferences set, it will use your system default.

Screenshot 2025-12-13 at 11 31 14 AM

Users who can login can override your choice of light/dark link colors, to accommodate folks who might require higher contrast, might have Color Vision Deficiency, or just like things to look the way they like.

You as the admins control the header color, but each user who can login has control over their light/dark link colors via their Account > Edit Profile screen.

Screenshot 2025-12-13 at 11 30 32 AM

If they do not choose any, they will inherit whatever the system settings are from the Branding settings.

If you have any CSS overrides via Admin Settings > Branding > Custom CSS, those will still apply as they get invoked after our CSS rules, although they might need some tweaking with !important - we're looking forward to the feedback on that.

What's Changed

New Contributors

Full Changelog: v8.3.6...v8.3.7

Contributors

uberbrady, snipe, and 5 other contributors
Loading

v8.3.6

v8.3.6

Choose a tag to compare

View all tags
@snipe snipe released this 24 Nov 13:02
v8.3.6
58a47cb

Caution

For some reason, Github's built-in redirect from snipe/snipe-it to grokability/snipe-it has stopped working. If you're trying to upgrade or pull and you get a "not found" response or a login prompt from Github, do the following to set your origin to the correct Github URL:

git remote remove origin
git remote add origin https://github.com/grokability/snipe-it
git fetch --all git reset --hard origin/master

Happy Monday! Snipe-IT v8.3.6 is out! We've made some improvements to the Unaccepted Items report, added file uploads to suppliers, and also added color tags to Locations, Companies, Departments, Suppliers, Categories, and Manufacturers. (Check out the docs here.) The new tag_color field is also available via the API for the affected object types.

e508c028a290c33e58cd03b87b8d52eeef7d0d2987443b8d2b17c63a24b5821b-frame_generic_light-15

We're also now sending an additional email header (X-System-Sender: Snipe-IT) for all notifications. This wouldn't affect anything related to notifications other than it allows clever folks to potentially apply filters on emails going to their inbox that have that header.

Additionally, if you have quite a lot of users and were unable to get the groups page to load in between v8.3.5 and v.8.3.6, that issue should be fixed. (It's a long, boring story related to default settings for max_input_vars and max_multipart_body_parts.) If you're still having problems, set your MAX_UNPAGINATED in your .env to something under 5000.

We know this isn't ideal, since being able to add users to from the groups page was a great new feature, but for users with very large user sets, this was a bit of a dealbreaker. Don't worry - we're working on figuring out a way that makes sense from a UX perspective. (For example, "select all users" when the user list is paginated would take a very long time, since you'd have to select them all individually.)

API changes

  • Added tag_color to Locations, Companies, Departments, Suppliers, Categories, and Manufacturers
  • If you were incorrectly passing the filter parameter to the Assets or Users endpoints (for example, /api/v1/users?filter=email:you@example.org), it would previously 500. It now returns a validation error, as that endpoint is looking for JSON (for example /api/v1/users?filter={"email":"you@example.org"}.)

What's Changed

New Contributors

Full Changelog: v8.3.5...v8.3.6

Contributors

uberbrady, joelpittet, and 5 other contributors
Loading

v8.3.5

v8.3.5

Choose a tag to compare

View all tags
@snipe snipe released this 10 Nov 14:12
v8.3.5
391aa30

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater, 8.3+ recommended.

Happy Monday! This release better handles how the system handles partially broken LDAP configurations, makes some improvements to notifications, adds the ability to set 2D barcodes to non-URL values, revamps the permission groups section, and tightens up some other UI elements.

Screen.Recording.2025-11-06.at.8.45.26.PM.mov
Screen.Recording.2025-10-25.at.6.37.18.PM.mov

(Note: The add-users section looks like the first video, not this one.)

Screen.Recording.2025-10-25.at.6.39.07.PM.mov

Quick mobile update: Progress is moving along quickly! We don't yet have a timeline for when TestFlights will be available, but we'll let you know here, on our social media (Bluesky & Mastodon), and on our discord.

And as always, you can see what we're working on and what's up next via our Milestones.

Breaking API change:

We did make a change to the API in #18150 that slightly changes the shape of the response. If you're using the Departments API and depend on the payload on PUT or PATCH responses, please update your code accordingly. (It now returns in the same shape as a GET request.)

What's Changed:

New Contributors

Full Changelog: v8.3.4...v8.3.5

Contributors

uberbrady, snipe, and 8 other contributors
Loading