fix(ci): hash root configs and infra fixtures into the Turbo cache #360
No reviewers
Labels
No labels
dependencies
major
security-pin
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
trails-cool/trails!360
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/turbo-cache-inputs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
CI keeps the Turbo cache between runs (
/ci-cache). A cache hit replays the old result. Turbo hashed only the files inside each package, so a change to one of these files got a cached green result for typecheck, lint and test:tsconfig.base.json,vitest.shared.ts,vitest.setup.ts,eslint.config.js(every package uses them)infrastructure/scripts/poi-selectors.sqlandinfrastructure/brouter-host/poi-extract/osmium-filters.txt(the map-core sync tests read them)Change
globalDependencies.@trails-cool/map-core#test. The declaration is in the rootturbo.json, so this PR changes no file belowpackages/and starts no preview deployment.Verification
turbo run … --dry=json, task hashes before and after a one-line change:vitest.shared.ts,vitest.setup.ts,tsconfig.base.json,eslint.config.jspoi-selectors.sql,osmium-filters.txtmap-core#testchangesinfrastructure/docker-compose.yml,README.mdCost: the first CI run after the merge has no cache hits. After that, the cache misses only when one of these files changes.
🤖 Generated with Claude Code