From eb6a5cc8b6b15ecbd8e59dc9f5f3b5882fc305ff Mon Sep 17 00:00:00 2001 From: Patryk Bujna Date: Mon, 20 Jul 2026 15:12:57 +0200 Subject: [PATCH] Make release splunk_versions a required input (no fleet default) The `splunk_versions` input in the reusable release.yml defaulted to "9.0,9.1,9.2,9.3,9.4". That default was unsafe as a fleet-wide value: it declared Splunkbase compatibility with Splunk 9.0/9.1 (which ship Python 3.7) and omitted all 10.x releases, so a caller that relied on the default would silently claim an incorrect support matrix. Make the input `required: true` with no default so every caller must declare its own real, validated compatibility explicitly, and expand the description to explain why. Existing callers (apius_lang_entropy, the splunk-app-template caller) already pass splunk_versions, so this is a no-op for them and a guardrail for future apps. --- .github/workflows/release.yml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 9cd278e..62ffc6a 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -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`