Skip to content

fix(deps): update grokability/snipe-it v8.6.1 → v8.6.2#2512

Open
truecharts-admin wants to merge 1 commit into
mainfrom
renovate/grokability-snipe-it-8.6.x
Open

fix(deps): update grokability/snipe-it v8.6.1 → v8.6.2#2512
truecharts-admin wants to merge 1 commit into
mainfrom
renovate/grokability-snipe-it-8.6.x

Conversation

@truecharts-admin

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
grokability/snipe-it patch 8.6.18.6.2

Release Notes

grokability/snipe-it (grokability/snipe-it)

v8.6.2

Compare Source

[!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: grokability/snipe-it@v8.6.1...v8.6.2


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@Crow-Control Crow-Control left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved automated PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants