Skip to content

fix: bump matrix version#509

Open
mkolasinski-splunk wants to merge 1 commit into
developfrom
fix/bump-matrix-version
Open

fix: bump matrix version#509
mkolasinski-splunk wants to merge 1 commit into
developfrom
fix/bump-matrix-version

Conversation

@mkolasinski-splunk

Copy link
Copy Markdown
Contributor

Description

This PR bumps matrix version to 3.2 including Splunk 10.4

Checklist

  • README.md has been updated or is not required
  • push trigger tests
  • manual release test
  • automated releases test
  • pull request trigger tests
  • schedule trigger tests
  • workflow errors/warnings reviewed and addressed

Testing done

(for each selected checkbox, the corresponding test results link should be listed here)

@mkolasinski-splunk mkolasinski-splunk requested a review from a team as a code owner June 26, 2026 14:53

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7c47d405ad

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

persist-credentials: false
- id: matrix
uses: splunk/addonfactory-test-matrix-action@v3.1
uses: splunk/addonfactory-test-matrix-action@v3.2

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Pin the matrix action to the 10.4 tag

In workflow runs that rely on needs.meta.outputs.matrix_Splunk, this ref still resolves to upstream v3.2/action.yml, which runs the Docker image ...:v3.2.0; that tag's splunk_matrix.conf still has LATEST = 10.2 and no [10.4] entry, while v3.2.1 is the release containing Splunk 10.4. As a result, the bump does not actually add 10.4 coverage, so scheduled/latest-Splunk test matrices continue testing 10.2 until this is pinned to the tag/image that contains the 10.4 matrix.

Useful? React with 👍 / 👎.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant