Skip to content

Commit b0ed95e

Browse files
docs: small adjustment to the runbook (#255)
1 parent 8c41e5d commit b0ed95e

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

runbooks/update_appinspect_cli_action.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ Once Splunk AppInspect team releases AppInspect CLI - we need to make sure that
1010
- check [release notes](https://dev.splunk.com/enterprise/docs/relnotes/relnotes-appinspectcli/whatsnew/) for the new version add release notes link in the PR comment
1111
- make sure that the pipeline is green
1212
- if not - investigate why and report and issue to the AppInspect team
13-
- determine which version of `appinspect-cli-action` needs to be released based on the PR
14-
- if it is a bug fix - change "chore" to "fix" in the title of the PR and skip [update section](#update-splunkaddonfactory-workflow-addon-release)
15-
- if it is a new feature - change "chore" to "feat" in the title of the PR
13+
- determine which version of `appinspect-cli-action` needs to be released based on the [splunk-appinspect release](https://dev.splunk.com/enterprise/docs/relnotes/relnotes-appinspectcli/whatsnew/)
14+
- if it is a bug fix release (E.g. v3.6.0 > v3.6.1) - change "chore" to "fix" in the title of the PR and skip [update section](#update-splunkaddonfactory-workflow-addon-release)
15+
- if it is a minor release (E.g v3.6.0 > v3.7.0) - change "chore" to "feat" in the title of the PR
1616
- get review from the team
1717
- "Squash and merge" the PR
1818
- wait for the release
@@ -23,6 +23,9 @@ Once Splunk AppInspect team releases AppInspect CLI - we need to make sure that
2323
- create a PR in this repository with a new version of the action ([example PR](https://github.com/splunk/addonfactory-workflow-addon-release/pull/247))
2424
- make sure that PR is towards `main` branch
2525
- make sure that the pipeline is green
26+
- determine which version of `appinspect-cli-action` needs to be released based on the PR
27+
- if it is a bug fix or dependecnies update - "fix" in the title of the PR
28+
- if it is a feature release - "feat" in the title of the PR
2629
- attach a link to a test run of reusable workflow
2730
- get review from the team
2831
- "Squash and merge" the PR

0 commit comments

Comments
 (0)