Skip to content

Make release splunk_versions required (drop unsafe fleet default) #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pbujna-apius merged 1 commit into from
Jul 20, 2026
Merged

Make release splunk_versions required (drop unsafe fleet default) #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,10 +57,13 @@ on:
description: >-
Comma-separated Splunk versions the release is compatible with, sent
as the Splunkbase Release API `splunk_versions` field (required by
the API).
required: false
the API). No default: every caller must declare its own real
compatibility explicitly. A blanket fleet default is unsafe -- it
would silently claim support for versions the app has not been
validated against (e.g. Splunk 9.0/9.1 ship Python 3.7) and omit
newer 10.x releases.
required: true
type: string
default: "9.0,9.1,9.2,9.3,9.4"
cim_versions:
description: >-
Optional comma-separated CIM versions, sent as the `cim_versions`
Expand Down
Loading