You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR removes `artifact-registry` step from the pipeline as we don't
need Docker containers with add-on builds in the ghcr.io. It is not used
in the infra anywhere. Also clean up README.md.
Test run:
https://github.com/splunk/splunk-add-on-for-mysql/actions/runs/7669490177
---------
Co-authored-by: kdoroszko-splunk <kdoroszko@splunk.com>
**NOTE:** This stage will create a new release with the main branch code irrespective of the test-execution status hence before creating a new release via this stage make sure all stakeholders are aware before the release.
664
-
665
-
- Follow the below steps to create a manual release and publish the relevant packages:
666
-
667
-
- Go to "Actions" tab of your Github repo link.
668
-
669
-
- On the left side, you'd have **"publish-untested"** workflow mentioned. Click on this stage.
670
-
671
-
- Click on **"Run Workflow"**.
672
-
673
-
- Select the branch from which you to create the tag.
674
-
675
-
- Ideally, all our final code would be in the main branch. Hence, in majority of cases the branch would be "main" only.
676
-
677
-
- Provide the version in "Tag to release" textbox.
678
-
679
-
- Example, if you are releasing a new version v4.0.1 of your add-on, just enter **"4.0.1"** (just the dot delimited digits, do not prefix it with "v").
680
-
681
-
- Click on **"Run Workflow"**.
682
-
683
-
- Wait for a couple minutes for the build to be generated and published.
684
-
685
-
- Once the above stage completes, go to "Releases" section of your repo.
686
-
687
-
- Edit the release and write the relevant release notes you want to for your bugfix/ hotfix release and save the changes.
0 commit comments