CI: move to setup-nim-action@v6 (Nimby 0.2.0) - #99
Merged
Conversation
Nimby 0.2.0 makes workspaces explicit and refuses to create one inside a Git checkout, so installing in the checkout root no longer works. Create the workspace in the checkout's parent instead, so boxy sits inside it next to its dependencies and nim finds nim.cfg by walking up. Also drop -g. Under 0.2.0 a global install writes no nim.cfg at all, so packages land on disk but stay invisible to the compiler: the install step goes green and the build then fails with "cannot open file". docs.yml moves off jiro4989/setup-nim-action + nimble onto the same Nimby workspace and nim doc, matching build.yml. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Modern emsdk ships emcc.exe on Windows and no longer provides emcc.bat, so the hardcoded emcc.bat broke the Windows emscripten builds: Error: invocation of external compiler program failed. Requested command not found: 'emcc.bat -c -w ...' setup-emsdk@v14 installs the latest emsdk, so this landed on its own as emsdk drifted forward; it is unrelated to the Nimby v6 move. CreateProcess appends .exe when the name has no extension, so the bare emcc used by the non-Windows branch already resolves correctly on Windows. Both branches are now identical, so the split is gone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Moves CI to
treeform/setup-nim-action@v6, which ships Nim 2.2.10 with Nimby 0.2.0 bundled.This is not just a tag bump — Nimby 0.2.0 made workspaces explicit, which breaks the old commands.
The silent failure
nimby sync -g nimby.lockstill exits 0 under 0.2.0, but writes nonim.cfganywhere. Packages land in~/.nimby/pkgsinvisible to the compiler, and the build fails later with a misleadingError: cannot open file: bitty. Verified against the real v6 toolchain.So
-gis dropped in favour of a real workspace created in the checkout's parent — that placement is load-bearing: a workspace underRUNNER_TEMPinstalls the packages but the build won't see them.docs.yml
Migrated off
jiro4989/setup-nim-action@v1+nimbleonto the same Nimby workspace andnim doc, so both workflows use one toolchain. Dropped the unusednim-version: 'stable'env (v6 requires an exact version and this was never passed to the action).Verification
Every
run:step was parsed from these YAML files and executed against the bit-identical v6 artifact (SHA-256 matched the release asset), in a sandbox withUSERPROFILEredirected:build.yml— workspace + sync + all 19 native example compiles passheart.nim→ real.wasm/.js/.html/.data)docs.yml— full run, produces the expected.gh-pagestree withindex.htmlLocal runs were Windows-only; this PR's CI covers ubuntu/macOS.
🤖 Generated with Claude Code