chore: bump version to 0.1.9 for the game-ci test --docker feature (#95) - #96
Merged
Merged
Conversation
Real gap found while converting unity-test-runner to a thin wrapper: cliVersion=latest resolves to whatever GitHub Release is marked latest, not main - #95 merged to main but no release was ever cut for it, so every consumer defaulting to "latest" was still getting v0.1.8's binary, which has no --docker/--local flags on `test` at all (confirmed via a real CI run: yargs reported them as unknown arguments).
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Aug 18, 2026
Merged
frostebite
added a commit
that referenced
this pull request
Aug 18, 2026
Docker test runs on unity-test-runner's thin-wrapper PR fail near- instantly with zero visible stdout - only two 'cat: no such file' stderr lines from the very end of test.sh's loop body, meaning the script reaches its last lines but nothing from mkdir/echo/unity-editor earlier in the script is visible at all, and the whole thing completes in well under a second (confirmed via job log timestamps) - too fast for Unity to have actually launched. Ruled out so far: the version-pin gap (#96, fixed), the eval/array bug in the coverage flags (#97, fixed) - this is a third, still-unidentified issue. set -x traces every command to stderr, which (unlike stdout) is rendering promptly in the CI log, to find the actual failure point in the next run. Temporary - will be removed once root-caused.
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.
Real gap found while converting
unity-test-runnerto a thin wrapper:cliVersion=latestresolves to whatever GitHub Release is marked latest, notmain— #95 merged tomainbut no release was ever cut for it, so every consumer defaulting to"latest"was still gettingv0.1.8's binary, which has no--docker/--localflags ontestat all. Confirmed via a real CI run onunity-test-runner's thin-wrapper PR: yargs reported them as unknown arguments and every job failed.This just bumps the version; a GitHub Release (
v0.1.9) needs to be cut from this commit once merged to actually publish the binaries.