Update snipe/snipe-it Docker tag to v7.1.15 #69
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/snipe-snipe-it-7.x
branch
from
8e00d25 to
41fb799
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/snipe-snipe-it-7.x
branch
from
41fb799 to
e4fd199
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/snipe-snipe-it-7.x
branch
from
e4fd199 to
2b34144
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/snipe-snipe-it-7.x
branch
from
2b34144 to
3cc445d
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/snipe-snipe-it-7.x
branch
from
3cc445d to
9024f9c
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/snipe-snipe-it-7.x
branch
from
9024f9c to
88c2d1b
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/snipe-snipe-it-7.x
branch
from
88c2d1b to
e20a5cb
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v7.0.7->v7.1.15Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
snipe/snipe-it (snipe/snipe-it)
v7.1.15Compare Source
Happy Monday, everyone! This is a bugfix release, mostly for folks running docker who only can deploy via tagged releases. We also fixed an issue with asset models not displaying on the listing page in some circumstances, fixed a few issues related to the recent MS Teams webhook deprecations, and handled an issue where uploaded asset files could not be deleted properly, plus a few visual tweaks for the signature pad.
What's Changed
via()channel for MS Teams (deprecated) by @Godmartinz in https://github.com/snipe/snipe-it/pull/15816filestableon assets by @snipe in https://github.com/snipe/snipe-it/pull/15819migrate:rollbackissues by @marcusmoore in https://github.com/snipe/snipe-it/pull/15840created_byand date for bulk user delete/checkin by @snipe in https://github.com/snipe/snipe-it/pull/15845Join the Community!
New Contributors
Full Changelog: snipe/snipe-it@v7.1.14...v7.1.15
v7.1.14: - Security ReleaseCompare Source
We seem to be getting a lot of mileage from that gif these days. 🫠
This is a security release that handles several CVEs, including CVE-2024-52301, which was just patched in the Laravel core yesterday.
While hosted customers were NOT affected (we do not have
register_argc_argvenabled on any of our servers), self-hosted community users and support-only customers are encouraged to upgrade as soon as possible, or at the very least make sure that setting is not enabled in yourphp.ini.In addition to the security patches, we have also added some new features, such as:
As always, still lots more on deck.
PS - we will likely be discontinuing posting updates on our Twitter account moving forward. Instead, find us in these other places:
What's Changed
Model::reguard()to importer by @marcusmoore in https://github.com/snipe/snipe-it/pull/15603updated_atfor sort in users API by @snipe in https://github.com/snipe/snipe-it/pull/15671$locationin LDAP sync command by @uberbrady in https://github.com/snipe/snipe-it/pull/15672strtolower()by @NebelKreis in https://github.com/snipe/snipe-it/pull/15687Company::getIdForCurrentUser()to return null in certain scenarios by @marcusmoore in https://github.com/snipe/snipe-it/pull/15691manufactuer_idby @Godmartinz in https://github.com/snipe/snipe-it/pull/15722livewire v3.5.9 => v3.5.12by @Godmartinz in https://github.com/snipe/snipe-it/pull/15712admin_cc_emailvalidation to allow an array by @Godmartinz in https://github.com/snipe/snipe-it/pull/15756${var}deprecation warning in License model by @jerm in https://github.com/snipe/snipe-it/pull/15758New Contributors
Full Changelog: snipe/snipe-it@v7.0.13...v7.1.14
v7.0.13Compare Source
Happy Wednesday, everyone! We're pleased to announce Snipe-IT v7.13 is out. The most notable fix in this release is for folks who suddenly couldn't create asset models with the same name but different model number. That was a temporary issue in validation and should be fixed now.
We've also added the long-requested ability to sort numerically on numeric custom fields. (Folks who are not using MySQL/MariaDB, please let us know if this breaks stuff for you, even though we don't officially support non-MySQL databases.)
We've also added a new bulk option for users, which is the ability to print all items associated with multiple selected users, if that's the sort of thing you're likely to do.
And finally, on most list views, you can now see (and sort by) which administrator created the item.
We've added a
created_byfield to additional endpoints. This field replaces the previoususer_idAPI object, which was only being returned in a few places. Theuser_idobject will still be returned as normal, but you should plan on making that switch in your API integrations moving forward, as it will eventually be removed.What's Changed
CustomFieldSetDefaultValuesForModelcomponent by @marcusmoore in https://github.com/snipe/snipe-it/pull/15486undeployablewhen editing by @snipe in https://github.com/snipe/snipe-it/pull/15492status labelnot updating by @Godmartinz in https://github.com/snipe/snipe-it/pull/15531user_idtocreated_byby @snipe in https://github.com/snipe/snipe-it/pull/15519$logActionfor user file upload by @snipe in https://github.com/snipe/snipe-it/pull/15555action_datetocreated_atin activity report by @snipe in https://github.com/snipe/snipe-it/pull/15561Full Changelog: snipe/snipe-it@v7.0.12...v7.0.13
v7.0.12Compare Source
What's Changed
)being added to expected asset checkin report email header by @marcusmoore in https://github.com/snipe/snipe-it/pull/15336snipeit:remove-explicit-eolscommand by @Godmartinz in https://github.com/snipe/snipe-it/pull/15065acceptance-remindercommand by @Godmartinz in https://github.com/snipe/snipe-it/pull/15375start_dateandend_dateto user bulk edit by @snipe in https://github.com/snipe/snipe-it/pull/15396New Contributors
Full Changelog: snipe/snipe-it@v7.0.11...v7.0.12
v7.0.11Compare Source
Happy Thursday everyone! This release comes with a bunch of small UX/UI improvements, and a few additional features, including the ability to optionally update the asset's status on quick scan checkin.
We've also added the ability to play sounds on the "quick" bulk tasks like auditing for better accessibility. (You will have to enable this in your profile.)
We've also added a command-line utility that can help some folks who may have used the API to checkout assets without specifying an
assigned_type, and could get a 500 error when trying to view those assets. (We have since improved the API validation to require theassigned_type, but older assets created via API could have had this issue.) See the docs on that utility here.Up next, the ability to checkout accessories to assets and locations. The functionality has been built, but there are some safeguards we still have to put in to make sure you cannot delete locations or assets that still have accessories associated with them. We have a PR up for that and are working on it.
What's Changed
MayContainCustomFieldsTrait to Asset Update Request by @spencerrlongg in https://github.com/snipe/snipe-it/pull/15198Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.