Fix CI: Docker builds fail (no package-lock.json) + backend tests fail (--coverage as path pattern) - #5
Merged
Conversation
…l theme, add /about page Co-authored-by: mesayanroy <169074736+mesayanroy@users.noreply.github.com>
… titles in Navbar, BNB→BIN Co-authored-by: mesayanroy <169074736+mesayanroy@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update frontend for professional appearance and navigation
Fix CI pnpm/npm mismatch + professional frontend redesign with dedicated nav pages
Mar 14, 2026
…PM_BAD_PM_VERSION CI failure Co-authored-by: mesayanroy <169074736+mesayanroy@users.noreply.github.com>
Copilot
AI
changed the title
Fix CI pnpm/npm mismatch + professional frontend redesign with dedicated nav pages
Fix CI: remove duplicate pnpm version causing ERR_PNPM_BAD_PM_VERSION on all jobs
Mar 14, 2026
… update lockfile Co-authored-by: mesayanroy <169074736+mesayanroy@users.noreply.github.com>
Copilot
AI
changed the title
Fix CI: remove duplicate pnpm version causing ERR_PNPM_BAD_PM_VERSION on all jobs
Fix CI: missing Mar 14, 2026
uuid dep in backend, missing @types/jest + test tsconfig in CLI
…S2742) Co-authored-by: mesayanroy <169074736+mesayanroy@users.noreply.github.com>
Copilot
AI
changed the title
Fix CI: missing
Fix CI: backend typecheck TS2742 + missing uuid dep + CLI jest types
Mar 14, 2026
uuid dep in backend, missing @types/jest + test tsconfig in CLICo-authored-by: mesayanroy <169074736+mesayanroy@users.noreply.github.com>
Copilot
AI
changed the title
Fix CI: backend typecheck TS2742 + missing uuid dep + CLI jest types
Fix CI: backend test suite fails due to jest treating Mar 14, 2026
--coverage as a path pattern
Co-authored-by: mesayanroy <169074736+mesayanroy@users.noreply.github.com>
Copilot
AI
changed the title
Fix CI: backend test suite fails due to jest treating
Fix CI: Docker builds fail (no package-lock.json) + backend tests fail (--coverage as path pattern)
Mar 14, 2026
--coverage as a path pattern
mesayanroy
marked this pull request as ready for review
March 14, 2026 20:53
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.
Two independent CI failures on the same PR:
package-lock.jsonand usednpm ci --workspace, but the repo is a pnpm workspace (pnpm-lock.yamlonly).pnpm test -- --coverageforwards--to jest, making jest treat--coverageas a file path pattern that matches nothing.Docker Dockerfiles (
devops/Dockerfile.backend,devops/Dockerfile.frontend)RUN corepack enableto activate pnpm from the"packageManager"field inpackage.jsonCOPY package.json package-lock.json→COPY package.json pnpm-lock.yaml pnpm-workspace.yamlpackage.jsonfiles before install (pnpm needs all manifests to validate the lockfile)npm ci --workspace=<pkg>→pnpm install --frozen-lockfile --filter <pkg>npm -w <pkg> run build→pnpm --filter <pkg> run buildBackend production stage retains
npm install --omit=dev— noworkspace:*cross-deps, so a standalone install from the copiedpackage.jsonis sufficient. Frontend production stage was already correct (Next.js standalone output is self-contained).Backend test configuration (
backend/package.json,.github/workflows/ci.yml)"collectCoverage": trueto jest config so coverage is always emitted bypnpm testpnpm test -- --coverage→pnpm test💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.