3 people 64b2cf0577 fix(ci): add yarn prisma generate before cache key generation (#26439) ...

This ensures consistent cache keys between the Build Web App job and E2E
shards by running yarn prisma generate before generating the cache key.

The issue was that packages/prisma/enums/index.ts is:
1. Generated by yarn prisma generate
2. In .gitignore (not committed to git)
3. Included in the SOURCE_HASH (matches packages/**/**.[jt]s)
4. NOT excluded from the hash

E2E jobs already run yarn prisma generate before cache-build, but the
Build Web App job did not, causing different cache keys in the same
workflow run.

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>

2026-01-04 21:38:22 -03:00

..

actions

refactor: detach yarn prisma generate from yarn-install action (#26382)

2026-01-01 23:00:56 -03:00

ISSUE_TEMPLATE

Create platform.md

2025-04-09 12:31:43 +02:00

matchers

Improves reported type errors on CI (#7813)

2023-03-28 13:12:40 -07:00

workflows

fix(ci): add yarn prisma generate before cache key generation (#26439)

2026-01-04 21:38:22 -03:00

CODEOWNERS

chore: CODEOWNERS Change Platform -> Consumer (#26160)

2025-12-23 19:18:42 +00:00

labeler.yml

chore: Updated labeler to v5 (#15127)

2024-05-20 14:08:50 +01:00

oasdiff-err-ignore.txt

feat: add session endpoint and booking access pbac (#24637)

2025-12-04 05:45:17 +00:00

PULL_REQUEST_TEMPLATE.md

chore: pr-template updates to include demonstrations (#19533)

2025-02-25 13:01:39 +00:00