Automate release #461
Automate release #461
Conversation
9f30409 to
14502b5
Compare
14502b5 to
dbdd625
Compare
39bc098 to
32eb603
Compare
There was a problem hiding this comment.
FYI: there is a typo in instruction: GITHUB_PAT -> GH_PAT
I saw that on your fork, branch build wasn't triggered, do you know why? On my fork, build was also not triggered. I tried also with the workflow_run and that would require splitting our make release workflow into two, so I abandoned that.
EDIT: somehow build was triggered now :D
Unfortunately, after 7 retries I was not able to run release successfully on my fork, I will discuss that offline :)
EDIT: After 10th execution and applied fixes finally I got it!
|
Do you have changelog generated for our repo which is not empty? Could you share it with me?
^ this doesn't work for me |
This reverts commit 1087be1.
46df89c to
8b8f9f7
Compare
Description
Changes proposed in this pull request:
grenfor release note generationTesting
You would need to clone, change a few things and push it to your main brach
GH_PAT- personal access token with permissions to commit to the repositoryGCS_CREDS- base64 encoded GCP credentials in JSON format for GCS write access.goreleaser.ymlrelease.github.ownerto your usernameblobs[0].bucketto a test bucket (you can usecapactio-release-testingI used)dockers[0].image_templatesto point to your GHCR.github/workflows/branch-build.yaml, so I didn't have to deal with the images pushed there.hack/release-charts.shchangeCAPACTIO_OFFICIAL_BUCKETenv to a test bucket (it must have a valid Helm repoindex.yaml, you can usecapactio-release-testingI used).With these changes, you should be able to test the workflow. Trigger it from
mainand provide eg.0.5.0as the version. It should create a release commit onmain, create a release branchrelease-0.5, push a commit with the Capact image SHA there and tag it. Also, a GitHub release should be created (the release notes will be empty, as your fork most probably does not have any merged PRs/issues).You can also test a patch release scenario, by triggering the workflow from the
release-0.5branch and providing0.5.1version.My runs:
0.5.0release - https://github.com/Trojan295/capact/runs/3423994881?check_suite_focus=true0.5.1release - https://github.com/Trojan295/capact/runs/3424068496?check_suite_focus=trueExample release notes generated by
gren- https://github.com/Trojan295/capact/releases/tag/untagged-a04325e324cfb3cb0597Related issue(s)
Resolves #444