Fix build containers workflow - update Go version, dependencies, and triggers#33
Merged
RelativeSure merged 2 commits intoSep 8, 2025
Merged
Conversation
…ove triggers Co-authored-by: RelativeSure <67839982+RelativeSure@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Please fix the build containers workflow. IT does not automatically start after merging the bump version PR. If manually run,
Backend fails:
Run docker/build-push-action@v6
GitHub Actions runtime token ACs
Docker info
Proxy configuration
Buildx versio...
Fix build containers workflow - update Go version, dependencies, and triggers
Sep 8, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This PR fixes critical issues in the build containers workflow that were preventing successful Docker image builds for both backend and frontend components.
Issues Fixed
Backend Build Failure
The backend Docker build was failing with:
Root Cause: The
backend/Dockerfilewas usinggolang:1.23-alpinewhilego.modrequires Go 1.24.Fix: Updated Dockerfile to use
golang:1.24-alpineto match the project requirements.Frontend Build Failure
The frontend Docker build was failing with:
Root Cause: The frontend Dockerfile was using
npm ci --only=productionwhich excludes dev dependencies likevitethat are required for the build process.Fix: Changed to
npm ciwithout the production flag to install all dependencies including dev dependencies needed for building.Workflow Trigger Issues
The build containers workflow was not automatically triggering after merging version bump PRs.
Fix: Enhanced the workflow with multiple trigger mechanisms:
release: [published]triggerpushtrigger for version file changes (VERSION, package.json, go.mod)workflow_runtrigger as backup when release workflow completesTrivy Security Scanner
The Trivy vulnerability scanner was causing workflow failures when SARIF upload couldn't find the results file.
Fix: Made SARIF upload conditional with
if: always() && hashFiles('trivy-results.sarif') != ''Technical Changes
golang:1.23-alpinetogolang:1.24-alpine--only=productionflag fromnpm cicommandTesting
✅ Backend builds successfully with Go 1.24
✅ Frontend builds successfully with full dependency installation
✅ All workflow triggers are properly configured
✅ Consistent Go version across all workflows (CI, release, build-containers)
The workflow will now automatically trigger on both new releases and version bump PR merges, ensuring container images are built and published correctly.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.