ci: formalize cloud release cycle for public SaaS - #1683
Conversation
Co-authored-by: Michael Sukkarieh <msukkari@users.noreply.github.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Co-authored-by: Michael Sukkarieh <msukkari@users.noreply.github.com>
Co-authored-by: Michael Sukkarieh <msukkari@users.noreply.github.com>
|
@msukkari your pull request is missing a changelog! |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 69ec473. Configure here.
|
|
||
| on: | ||
| push: | ||
| branches: ["main"] |
There was a problem hiding this comment.
Release tags skip production publish
High Severity
Official releases commit with [skip ci] before pushing the v*.*.* tag, and GitHub suppresses push workflows for that commit—including tag pushes. After dropping the main trigger, production cloud images no longer publish on the release cycle. The same skip also drops the release commit from the staging main workflow.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 69ec473. Configure here.
| environment: prod | ||
| git_ref: ${{ github.ref }} | ||
| docker_tags: | | ||
| type=raw,value=main,enable=${{ github.ref == 'refs/heads/main' }} |
There was a problem hiding this comment.
Manual dispatch publishes no image tags
Medium Severity
Both remaining docker_tags rules enable only when github.ref is a version tag. workflow_dispatch defaults to a branch ref, so metadata emits an empty tag list and the reusable build still pushes. docker/build-push-action then fails because a tag is required.
Reviewed by Cursor Bugbot for commit 69ec473. Configure here.


Fixes SOU-2279
Summary
v*.*.*release tags while retaining manual dispatch.mainpushes using thestagingGitHub Environment and staging ECR repository.Unreleasedchangelog entry.Validation
git diff --checkand confirmed no stale production-on-maincomment remains.Linear issue: SOU-2279
Summary by cubic
Formalizes the cloud release cycle so production images publish only on
v*.*.*release tags, whilemainpushes now build the staging image instead of production.mainbranch trigger and its image tags from the production cloud workflow; manual dispatch is unchanged.mainpushes into thestagingGitHub Environment and staging ECR repository.Written for commit 69ec473. Summary will update on new commits.