Repository navigation
ci: use local Mac with cloud fallback and patch production dependencies - #100
Merged
Merged
Conversation
hmmhmmhm
marked this pull request as ready for review
October 6, 2026 05:23
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.
CI prefers the repository's
personal-mac-ground.codesrunner after a short GitHub-hosted status check. Offline or missing runners, status-query failures, and external PRs retain the original cloud runner. Busy local runners remain eligible. The scoped read-only status secret is installed and expires 2027-01-04.Fix existing production dependency audit failures with Next/eslint-config-next 15.5.24, sharp 0.35.4 and patched transitive dependencies. @parcel/watcher 2.5.6 removes the vulnerable production micromatch/braces path using its upstream picomatch migration. Update existing dependency/lock policy expectations; keep audit rejection, coverage and all other CI checks enabled. Runtime CI/deployment uses Node 22, satisfying sharp's Node >=20.9 requirement.
Validation: production audit reports zero findings, policy/lock tests pass 26/26, and independent dependency review passed. Selector, host trust, shared-slot checks and actionlint passed; token-based local smoke passed. Full application CI: https://github.com/hmmhmmhm/ground.codes/actions/runs/37415744870 (latest attempt uses actual offline/cloud selection).
The local runner needs sufficient storage: verified region data alone occupies 8.355 GiB across 2,031 files, plus dependencies/build outputs. The first local application run passed audit then exhausted storage while materializing data. Allow about 15 GiB free until a successful full run measures peak usage. No datasets or tests are skipped. Selection occurs before queueing and cannot migrate an already-queued/running job after a later disconnect.