Skip to content

Conversation

@mkolasinski-splunk
Copy link
Contributor

Description

(PR description goes here)

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 and others added 17 commits September 25, 2025 13:38
### Description

(PR description goes here)

### 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)
### Description
This PR introduces mechanism for splitting dev dependencies from
pyproject.toml and putting them to into dev_deps/requirements_dev.txt
file. This is breaking change and needs to be performed before relevant
repository template rollout.



### Checklist

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

### Testing done 
splunk/splunk-add-on-for-cisco-asa#465

splunk/splunk-add-on-for-amazon-web-services#1532
splunk/splunk-add-on-for-google-workspace#651

splunk/splunk-add-on-for-microsoft-office-365#895

splunk/splunk-add-on-for-microsoft-cloud-services#1363
### Description

We can start slowly decreasing the amount of max time spent. Let's start
with 5 hours.

### Checklist

- [x] `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

No testing was done.
…442)

### Description

Adopt validate-docs and upload-to-splunkbase reusable workflows.
This change doesn't affect current workflows and will be tested on
develop branch.

### 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)
### Description

This PR adds the GS scorecard job into reusable release. Do not merge
until 1.0.0 GS scorecard image is pushed to ecr

### Checklist

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

### Testing done 

https://github.com/splunk/splunk-add-on-for-microsoft-cloud-services/actions/runs/18752030521/job/53494778020
@mkolasinski-splunk mkolasinski-splunk force-pushed the test/reusable-wf-5_2-python-3_13 branch from ce17dcb to 8c7ee8f Compare November 24, 2025 11:57
@mkolasinski-splunk mkolasinski-splunk changed the base branch from develop to main November 24, 2025 12:47
@mkolasinski-splunk mkolasinski-splunk marked this pull request as ready for review November 24, 2025 12:47
@mkolasinski-splunk mkolasinski-splunk requested a review from a team as a code owner November 24, 2025 12:47
@mkolasinski-splunk mkolasinski-splunk changed the title fix: reusable wf 5 2 python 3 13 fix: reusable wf 5.2 python 3.13 adjustments Nov 24, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Nov 27, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants