-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: automate bumping ZITADEL version #43
Conversation
Co-authored-by: eliobischof <eliobischof@users.noreply.github.com>
This reverts commit cced733.
Co-authored-by: eliobischof <eliobischof@users.noreply.github.com>
This reverts commit d5e7bc4.
@eliobischof @fforootd can we merge this? Or do we need something? |
@livio-a why is it WIP again? https://github.com/zitadel/DevOps/issues/10#issue-1604411571 |
Probably only because of the open discussion above (version parsing), but for me it's ok if we merge the current state |
I resolved it |
* add bump ZITADEL workflow * use semanticoutput * test action * fix trigger * remove if * add token * syntax and typos * syntax * typos * typo * fix references * debug * reading multiple yaml keys is not supported * debug * fix read yaml usage * typo * don't fail on semver conditionals * fix action ref * typo * debug * update Chart.yaml * fix order * automerge and approve * [create-pull-request] automated change (zitadel#4) Co-authored-by: eliobischof <eliobischof@users.noreply.github.com> * Revert "[create-pull-request] automated change (zitadel#4)" This reverts commit cced733. * gh token scopes * test bump * [create-pull-request] automated change (zitadel#5) Co-authored-by: eliobischof <eliobischof@users.noreply.github.com> * Revert "[create-pull-request] automated change (zitadel#5)" This reverts commit d5e7bc4. * cleanup * remove newline * use app token --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: eliobischof <eliobischof@users.noreply.github.com>
contributes to #29
What's happening:
I created the PR from a fork for testing purposes, because the workflow is just activated when it's on the default branch.