Feat/tenant switcher shown when user other tenants not main#269
Conversation
…main > test coverage
|
Claude finished @michael-on-code's task —— View job E2E Coverage Check
Result: ✅ E2E Coverage — No IssuesNo new PR approved. |
mamigot
left a comment
mamigot
left a comment
There was a problem hiding this comment.
✅ E2E Coverage — No Issues
No new app routes were introduced. All existing coverage is intact.
The repo uses a pnpm patchedDependency:
patchedDependencies: { "google-drive-picker@1.1.29": "patches/google-drive-picker@1.1.29.patch" }
Both Dockerfiles copied only package.json + pnpm-lock.yaml before
`pnpm install --frozen-lockfile`, so pnpm read the patch reference from the
lockfile and failed to open the (not-yet-copied) patch file:
ENOENT: no such file or directory, open '/app/patches/google-drive-picker@1.1.29.patch'
Copy patches/ alongside the manifests, before install, in both Dockerfile and
e2e/Dockerfile so the patch file is present when pnpm hashes/applies it.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
fix(ci): copy patches/ before pnpm install (pnpm patchedDependency ENOENT)
Fix/1924
…ports-endpoint Fix/mentor id payload passed to reports endpoint
Fix/1904
Feat/tts endpoint now streamble
Fix/2022
|
Claude finished @michael-on-code's task —— View job E2E Coverage Check
Result: ✅ E2E Coverage — No IssuesNo new PR approved. |
mamigot
left a comment
mamigot
left a comment
There was a problem hiding this comment.
✅ E2E Coverage — No Issues
No new app routes were introduced. All existing coverage is intact.
|
Claude finished @michael-on-code's task —— View job E2E Coverage Check
Result: ✅ E2E Coverage — No IssuesNo new PR approved. |
mamigot
left a comment
mamigot
left a comment
There was a problem hiding this comment.
✅ E2E Coverage — No Issues
No new app routes were introduced. All existing coverage is intact.
|
Claude finished @michael-on-code's task —— View job Claude finished @michael-on-code's task —— View job E2E Coverage Check
Result: ✅ E2E Coverage — No IssuesNo new PR approved. |
mamigot
left a comment
mamigot
left a comment
There was a problem hiding this comment.
✅ E2E Coverage — No Issues
No new app routes were introduced. All existing coverage is intact.
|
Claude finished @michael-on-code's task —— View job E2E Coverage Check
Result: ✅ E2E Coverage — No IssuesNo new This branch was missing Journey 61 (LaTeX/Math Rendering) — added to
PR approved. |
mamigot
left a comment
mamigot
left a comment
There was a problem hiding this comment.
✅ E2E Coverage — No Issues
No new page.tsx routes were introduced in this PR. The mechanical coverage check passed with 550 checkpoints and 100% journey coverage (25/25 files mapped).
This branch was missing Journey 61 (LaTeX/Math Rendering) which was merged to main after this branch was cut. The missing e2e/journeys/61-latex-math-rendering.spec.ts, e2e/coverage.json, e2e/COVERAGE.md, and e2e/page-objects/chat.page.ts changes have been restored and committed to the branch.
PR approved.
michael-on-code
added
run-tests
7 participants
Checklist
Changes