Repository navigation
fix(ci): isolate native Windows app module scope - #17
Merged
Merged
Conversation
Open
8 tasks
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.
The first actual Windows qualification launch failed before editing because the extracted Nimbalyst app inherited this checkout’s
type: modulesetting. Its packaged CommonJS SQLite worker then rejectedrequireduring database startup.Extract and launch the app under a fresh runner temporary directory outside the checkout and enclosing ESM package scopes. Keep the actual working directory inside its isolated public workspace and avoid PowerShell’s automatic
$PROFILEvariable. App checksums, candidate admission, the restricted child environment, network boundary and installed-file verification stay unchanged.Validation: three real Node worker-resolution regressions, 39 source tests, 22 package tests, strict types, native build, and actionlint pass. The regressions use a representative CommonJS worker; native stderr records the actual packaged worker failure. Rebuilding still produces the exact same candidate SHA-256
9c7856ccdc8f1c8099bde0d872853247b1750c21807cbe9ebf2eabc82ddd5ec8. The actual Windows app retry follows this repair; these checks do not claim native acceptance.