Skip to content

fix(ci): unify CI/CD naming, parallelize builds, and fix runner warnings - #1088

Merged
AchoArnold merged 3 commits into
mainfrom
fix/unify-cicd-workflow
Nov 17, 2026
Merged

AchoArnold merged 3 commits into
mainfrom
fix/unify-cicd-workflow

Conversation

@AchoArnold

@AchoArnold AchoArnold commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Consolidate frontend and backend into one CI/CD workflow with consistent job, step, and Cloud Build display names and one README badge.
  • Run Run Integration Tests first, then Deploy API and Build Web in parallel. Deploy the frontend only after both succeed.
  • Build the frontend once, upload its static output, and deploy that exact artifact to Cloudflare and Firebase in parallel with independently reported results. Remove duplicate dependency installation/builds and the obsolete separate web workflow.
  • Fix Firebase's hosting directory from the old dist path to Nuxt's .output/public so both hosts publish the same output.
  • Fix the Go cache warning by explicitly hashing api/go.sum and tests/go.sum; pin every runner to ubuntu-26.04 to avoid the Ubuntu 26 migration warning.
  • Preserve main-push-only deployment and PR integration/web validation. Rename the unified workflow to ci.yaml and use github.run_id for both API and frontend versions so renaming does not restart the version sequence.
  • Serialize runs per ref to prevent overlapping production deployments, scope Google OIDC permissions to API deployment, and stop ignoring failed database seeding.

Pipeline

Run Integration Tests
  ├─ Deploy API ─┐
  └─ Build Web ──┤
                ├─ Deploy Web (Cloudflare)
                └─ Deploy Web (Firebase)

Pull requests run the integration and web build/validation jobs without deploying.

Verification

  • actionlint passed with only its outdated Ubuntu 26.04 runner-label warning filtered; the runner label was verified against the official GitHub runner-images documentation.
  • Repository YAML, formatting, end-of-file, and whitespace hooks passed; Firebase JSON passed Prettier.
  • Configuration assertions verified the dependency graph, parallelism, main-only deployment guards, permissions, matching artifact upload/download paths, Firebase/Cloudflare output paths, one build, shared Actions run-ID versioning with a local development fallback, updated workflow links, Go cache input files, and pinned runners.
  • Checked upstream action definitions for Go cache and artifact upload support.

The existing lockfile's minimum-release-age violation still blocks the Husky hook. Husky was skipped for this commit with explicit approval; dependencies and supply-chain policy were not changed. Live deployments require merging to main.

Build the web artifact alongside API deployment after integration tests, then deploy that artifact to both frontend hosts in parallel. Standardize names, publish one CI/CD badge, pin Ubuntu runners, and configure the Go module cache paths.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: a0fd7292-f3aa-4919-929f-d73c2ac0f0c2
@codacy-production

codacy-production Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

Not up to standards ⛔

🔴 Issues 2 high

Alerts:
⚠ 2 issues (≤ 0 issues of at least minor severity)

Results:
2 new issues

Category Results
Security 2 high

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: a0fd7292-f3aa-4919-929f-d73c2ac0f0c2
@greptile-apps

greptile-apps Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

Consolidates API and web delivery into one CI/CD workflow.

  • Integration tests stop when database seeding fails.
  • The site builds once and reaches both hosts after API deployment.
  • Cloud Build logs identify the API image and deployment steps.

No actionable issues were found.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  Tests[Run Integration Tests] --> API[Deploy API: main pushes only]
  Tests --> Build[Build Web]
  Build --> Artifact[Upload web build]
  API --> Cloudflare[Deploy Web: Cloudflare]
  API --> Firebase[Deploy Web: Firebase]
  Artifact --> Cloudflare
  Artifact --> Firebase
Loading

Reviews (1) · Last reviewed commit: "fix(ci): unify pipeline naming and paral..." · Reviewed by Greptile

Rename the workflow to ci.yaml and update documentation links. Use the same repository-wide Actions run ID for API and web versions so renaming the workflow does not restart the version sequence.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: a0fd7292-f3aa-4919-929f-d73c2ac0f0c2
@AchoArnold
AchoArnold merged commit 4647417 into main Nov 17, 2026
6 of 9 checks passed
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 this pull request may close these issues.

1 participant