If you’re watching the Snipe-IT repo closely (which it’s totally fine if you aren’t – go be a normal person! Do normal people stuff!), you will have noticed some changes recently. Lots of older issues being closed, lots of them being resurfaced, lots of new categorizing of things, etc. We’ve decided to try something new for us. It’s going to get weird, a little...
Important! You should not have to do anything to continue using and upgrading Snipe-IT. Github’s redirects should handle everything for you. Don’t worry – this won’t affect you much (if at all), we’re just letting you know in case you have any bespoke integrations, or in case you get freaked out that the namespace has changed. Why the move? Moving the repo to...
Yesterday, we released v8.0.0 of Snipe-IT (and today, the inevitable v8.0.1)! While the feature list looks a little light for a major release, we had to tag it as v8 because the minimum PHP requirement changed – but I’ll explain more about that a bit further down. First, the fun stuff: Custom fields on checkin/checkout! (Documentation updates coming shortly) Breadcrumbs for better UX...
Just a few days ago, a patch for CVE-2024-52301 was to Laravel’s core, Laravel being the PHP framework we use here at Grokability for Snipe-IT. The patch for this security flaw was released in v7.1.14 earlier today. While hosted customers were NOT affected (we do not have register_argc_argv enabled on any of our servers), self-hosted community users and support-only customers are...
As you likely know by now, v7 of Snipe-IT dropped a few weeks ago. Those of you who have been with us for a long time know that those major version releases can be pretty tough. When you’re hoisting the underlying framework by several versions, upgrading dependencies, plus adding features, things can get messy fast. Making sure that we cover as many possible versions as possible for our...