Skip to content

Releases: grokability/snipe-it

v8.1.16

16 Jun 13:49
Compare
Choose a tag to compare

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater.

Happy Monday, everyone! This release fixes some bugs around maintenances and bulk editing custom fields, adds the ability create multiple maintenances at one time, and took some steps to speed some things up in some interfaces.

As we mentioned here on Github and on our blog, we're experimenting with a new way of handling issues, requests, etc here. We're trying to break as much as we can down into two-week sprints - you can see the past sprint we just closed here.

We'll also continue experimenting with the Roadmap view on Github in an ongoing effort to convey what we're currently working on, what longer-term features we're trying to find solutions for, and so on. (The roadmap view is a little cumbersome to manage on our end, but we'll keep trying.)

We didn't quite make all of the items in first sprint so they've been moved to the next one, but we'll get a better sense for that over time.

What's Changed

New Contributors

Full Changelog: v8.1.15...v8.1.16

Join the Community!

v8.1.15

02 Jun 17:38
Compare
Choose a tag to compare

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater.

Happy Monday everyone! This release offers some UX fixes, some API enhancements for consistency, and three new classes of things you can use the importer for: manufacturers, suppliers, and categories. See what's on deck for the next release here: https://github.com/grokability/snipe-it/milestone/26.

Important API header change:

In order to to make it easier for you folks to build all the great stuff you do with the Snipe-IT REST API, we've added a few additional headers on API requests. Now every API request will return the following headers regardless of whether you've hit your API limit and are now returning a 429 response:

Header Value
X-RateLimit-Limit The rate limit defined in your .env for API_THROTTLE_PER_MINUTE
X-RateLimit-Reset The reset in seconds
X-RateLimit-Remaining The remaining requests within the X-RateLimit-Reset
X-RateLimit-Reset-Timestamp The epoch timestamp for when the rate limit will reset
Retry-After The reset in seconds, same as X-RateLimit-Reset

Previous versions of the API would only return some of these headers if you were getting a 429 - too many requests response.

For example:

Screenshot 2025-06-02 at 6 30 02 PM

What's Changed

New Contributors

Join the Community!

Full Changelog: v8.1.4...v8.1.15

v8.1.4

23 May 12:29
Compare
Choose a tag to compare

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater.

Happy Friday! This release handles some wonkiness around notifications (slack and emails).

What's Changed

New Contributors

Full Changelog: v8.1.3...v8.1.4

v8.1.3

07 May 11:09
Compare
Choose a tag to compare

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater.

Happy Wednesday! This release fixes a few small bugs, updates a library dependency that had a CVE, and hopefully handles some of our docker users.

We're sorry this has been a hassle for the docker folks.

Dockerhub makes it surprisingly un-intuitive to keep your Dockerhub namespace when you switch a GH repo namespace. Why would we want to keep our old Dockerhub namespace, you ask? Good question! Turns out you can't move namespaces and keep your stars and pull counts, which we kinda want, since we're the original creators.

We had to undo some of the much faster build optimizations we had previously made for Docker people - they take almost an hour now - ouch. But we'll be revisiting that and speeding it back up in the next week.

To clarify, Docker folks should be pulling from snipe/snipe-it, not grokability/snipe-it. It's counter-intuitive, I know. Dockerhub won't let us move without losing literally a decade of pull and star stats. :(

What's Changed

New Contributors

Full Changelog: v8.1.2...v8.1.3

v8.1.2

05 May 10:28
Compare
Choose a tag to compare

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater.

Happy Monday! This tagged release should hopefully fix the docker builds that were not auto-pushing since the repo move. (We're still trying to find a way to get back to the old location where our 10M docker pulls and stars more accurately reflect reality, but Docker Hub doesn't make that particularly easy.)

We know the docker builds are running very slow right now, and we're working on speeding those up.

What's Changed

Full Changelog: v8.1.1...v8.1.2

v8.1.1

29 Apr 22:22
Compare
Choose a tag to compare

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater.

Hi again - did you miss us? :)

This is just a point release to smooth out a funky UI artifact on some screens and a few color fixes for dark-mode skins.

What's Changed

  • Fixed fieldset display if custom fields are not available by @snipe in #16827
  • Fixed Dark Mode color choices for fieldset links by @Godmartinz in #16797
  • Handle category being null in CheckoutableListener by @marcusmoore in #16799
  • Add audit button to BS table partial, redirect if asset won't validate by @snipe in #16828

Full Changelog: v8.1.0...v8.1.1

v8.1.0 - Security Release

29 Apr 12:55
Compare
Choose a tag to compare

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater.

Happy Tuesday! Hopefully everyone's power is back up and running after Europe's big power outage yesterday.

As you may have noticed, we've got a new address! We moved the Snipe-IT repo from snipe/snipe-it to grokability/snipe-it. You can read a little more about that on our blog, but the short version is that everything went smoothly, existing PRs and issues were moved, and redirects from the old repo address to the new digs should be automatic.

We now have file uploads for locations, the ability scope locations to company, the ability to seed common manufacturers, locations as a QR code destination, and we added the ability to add custom fields to audit screens (and a bunch more stuff detailed below.)

This release also fixes a ton of bugs, adds more accessibility controls, and addresses some additional security controls around printable lists of items and a vulnerability in Laravel File Validation. As this is a security release, we strongly recommend upgrading as soon as possible.

fixing-bugs

Added:

Improved

Fixed

Read more

v8.0.4

05 Mar 17:12
Compare
Choose a tag to compare

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater.

Happy Wednesday! One more tiny point release that addresses issues some folks might have run into on creating a new user via the "New" modal windows, some auditing errors if you don't have a notification webhook set, and some weird redirects with the new report templates on Snipe-IT installations that live in a subdirectory.

If you're having problem using the upgrade.php script with an error like Method Illuminate\Routing\Route:: breadcrumbs does not exist, please run git pull; composer install --no-dev; php upgrade.php, which will pull the latest code, install dependencies, and then run the upgrade script (which handles migrations, clearing caches, etc.)

Note

Please make sure you have changed your BS_TABLE_STORAGE value to localStorage in your .env and clear your cookies after upgrading. See the pinned issue #16136 for additional information.

What's Changed

  • Adds audit notification for MS Teams by @Godmartinz in #16414
  • Changed visited-link and link colors in default theme to be more accessible by @Godmartinz in #16413
  • Fixed custom report template route for installations in subdirectories by @marcusmoore in #16420
  • Fixed user create modal - check if $item is set by @snipe in #16427

Full Changelog: v8.0.3...v8.0.4

v8.0.3

04 Mar 21:22
Compare
Choose a tag to compare

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater.

Howdy folks! This is a small point release that handles a few small bugs that have surfaced over the past week.

If you're having problem using the upgrade.php script with an error like Method Illuminate \Routing \Route:: breadcrumbs does not exist, please run git pull; composer install --no-dev; php upgrade.php, which will pull the latest code, install dependencies, and then run the upgrade script (which handles migrations, clearing caches, etc.)

Note

Please make sure you have changed your BS_TABLE_STORAGE value to localStorage in your .env and clear your cookies after upgrading. See the pinned issue #16136 for additional information.

What's Changed

  • Added "Reminder" to subject line of follow up asset checkout emails by @marcusmoore in #16156
  • Fixed #16371 - incorrect count and missing name in acceptance reminder email by @snipe in #16375
  • Add some safety around the charset-detection and transliteration in backup restore by @uberbrady in #16376
  • Wrap long text in PDF export in tables by @snipe in #16378
  • Added ldap invert active flag by @azmcnutt in #16379
  • Avoid using authenticated user's email address in email partial by @marcusmoore in #16398
  • Adds Translation strings to General and Branding Settings by @Godmartinz in #16150
  • Fixed duplicate entries preventing LDAP sync from continuing by @Fiala06 in #15911
  • Refactored audit notification to mail, added test, added alerts check to scheduler by @Godmartinz in #16251
  • Fixed #16402 - localize "each" string in components tab on asset view by @snipe in #16403
  • Fixed #16386 - some fields not populating with user data on edit by @snipe in #16409
  • Fixed #16407 - weird layout on components for non super user by @snipe in #16410
  • Fixed regression from #16150 where branding page could not be saved by @snipe in #16412
  • Nicer model name formatting on RMB model not found by @snipe in #16415

New Contributors

Full Changelog: v8.0.2...v8.0.3

v8.0.2

27 Feb 12:30
Compare
Choose a tag to compare

Caution

This version of Snipe-IT REQUIRES PHP 8.2.0 or greater.

Howdy all! Just a small point release today to handle some tiny issues we've seen since the 8.0.0 release. We've also improved the look of the upgrader script to give you color support to make things a little clearer if something went wrong with your upgrade.

We've also changed the behavior of what happens when you edit an asset to a pending status. Previously, editing an asset to a non-deployable asset status would automatically check it in. Now, both deployable and pending status types will stay checked in (if they are checked out) and only archived and undeployable will automatically checkin assets. This is to account for use-cases like when an asset it out for repair should still technically be assigned to the user in question, as it will be returned once it comes back from repair.

Note

Please make sure you have changed your BS_TABLE_STORAGE value to localStorage in your .env and clear your cookies after upgrading. See the pinned issue #16136 for additional information.

What's Changed

New Contributors

Full Changelog: v8.0.1...v8.0.2