Merged
Conversation
Contributor
Author
cmcginley-splunk
approved these changes
Mar 5, 2026
Contributor
cmcginley-splunk
left a comment
There was a problem hiding this comment.
Good catch! Confirmed on my end that the suffixes used by Splunkbase on download have changed
pyth0n1c
approved these changes
Mar 5, 2026
Contributor
pyth0n1c
left a comment
There was a problem hiding this comment.
I have confirmed with the Splunkbase Team that this is an intentional change on their end/ Great catch, thanks Lou!
Approved.
This file contains hidden or 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
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.

Looks like Splunkbase changed some things, so metadata validation was hitting a ValueError and bailing out. See https://github.com/splunk/security_content/actions/runs/22721988462/job/65886387827?pr=3937 for example.