Conversation
The sync bot pushes dev and the beta tag with GITHUB_TOKEN, and GitHub does not trigger workflows from GITHUB_TOKEN events - so build-docker.yml never ran for bot syncs and no beta image was ever published. workflow_dispatch is the documented exception, so the bot now dispatches build-docker.yml explicitly for the beta tag and for dev after pushing. Image build + GHCR push only: there is no deploy step (servers pull the image manually; no staging/blue-green in this fork). Also: deploy.yml no longer runs on tag push (it mirrored main into a release branch and needs a GH_TOKEN secret that does not exist here); it is kept as workflow_dispatch for manual promotion. And the pre-release step no longer swallows failures with '|| true' - it checks for an existing release and fails loudly otherwise (every beta so far silently got no GitHub Release). Node bumped 22 -> 24 to match engines.
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_e9f08148-f153-4726-8c70-411bbb6c719e) |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe deployment workflow now requires manual dispatch. The upstream synchronization workflow uses Node.js 24, dispatches Docker image builds for the beta tag and dev branch, and creates the pre-release only when it does not already exist. ChangesWorkflow automation
Estimated code review effort: 2 (Simple) | ~10 minutes Sequence Diagram(s)sequenceDiagram
participant SyncWorkflow as sync-upstream.yml
participant GitHubActions as GitHub Actions
participant DockerWorkflow as build-docker.yml
participant Release as GitHub Release
SyncWorkflow->>GitHubActions: Dispatch beta Docker build
SyncWorkflow->>GitHubActions: Dispatch dev Docker build
GitHubActions->>DockerWorkflow: Build GHCR images
SyncWorkflow->>Release: Create pre-release if absent
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
1 participant
Fixes the dead half of the Sync Upstream & Deploy Beta pipeline.
Note
Medium Risk
Changes CI release and image-build orchestration; mis-dispatched builds or deploy workflow misuse could block beta artifacts or confuse promotion, but no application runtime code is touched.
Overview
Production deploy no longer runs on every tag push; it is
workflow_dispatchonly, with comments documenting that this fork expects manual image pulls and optional manual promotion via the existingreleasebranch merge (no auto-deploy).Upstream sync bumps the workflow Node version to 24 and fixes the broken beta image pipeline: after tagging
*-betaand pushingdev, it explicitlygh workflow run build-docker.ymlfor the beta tag and fordev, because pushes usingGITHUB_TOKENdo not start other workflows. Pre-releases are created only when missing (dropping|| trueso failures surface), and release notes now point at the GHCR image and manual server pull.Reviewed by Cursor Bugbot for commit dc36f01. Configure here.
Summary by CodeRabbit