Skip to content
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

Implement auto-creation of staging branch #55

Closed
iameli opened this issue Jul 25, 2022 · 0 comments · Fixed by #60
Closed

Implement auto-creation of staging branch #55

iameli opened this issue Jul 25, 2022 · 0 comments · Fixed by #60
Assignees

Comments

@iameli
Copy link
Contributor

iameli commented Jul 25, 2022

  • Upon an upstream project cutting a new semver release (make release or whatever), a new CI action gets kicked off
  • This CI action generates a new "version manifest" file based on the latest semver releases of all of the upstream projects listed in manifest.yaml
  • This version manifest then gets committed onto a new branch off of main named staging. This branch is always force-pushed, so there's just one commit to merge when we want to cut a release.
  • It should also open a PR, if one does not already exist, from staging to main.
  • When we want to cut a new Catalyst release, we simply merge that PR and CI takes care of publishing new images.
@iameli iameli changed the title Implement auto-creation of staging branch Implement auto-creation of staging branch Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants