Skip to content

Release 0.1.2: promote dev to main (Windows wildcard fix) - #1371

Merged
swapnilpaliwal-sd merged 2 commits into
mainfrom
dev
Sep 26, 2026
Merged

swapnilpaliwal-sd merged 2 commits into
mainfrom
dev

Conversation

@swapnilpaliwal-sd

Copy link
Copy Markdown
Contributor

Promote dev to main: release 0.1.2 (second attempt)

The first release build (#1368) passed on linux-x64, linux-arm64, darwin-arm64 and darwin-x64. It failed on win32-x64 on one new e2e check, path '*' leaf: Git Bash expanded * into the working directory's file names (#1369). That bug had been in every release on Windows; the extended e2e found it on its first Windows run.

Since then:

No rules or build files changed since the last build, so the engines built for #1368 should come back from the cache: this build should take minutes, not an hour. The five-platform e2e then runs again. When it is green, axiomcode-bot tags v0.1.2 and drafts the release.

Git Bash's runtime globs the arguments a native Windows process passes
it, since no shell did. The npm launcher and the MCP server start bash
with `*` unquoted, so `axiomcode path '*' X` reached the CLI as the
working directory's file names. The release e2e caught it on its first
Windows run.

withPython, the environment every launcher (CLI, MCP, hooks) hands to
bash, now adds noglob to MSYS on Windows, keeping any MSYS options the
user set. Verified on Windows Server 2022: `axiomcode path * square`
answered for file names before and for `*` after.
windows: stop Git Bash expanding '*' in the CLI's arguments (#1369)
@swapnilpaliwal-sd
swapnilpaliwal-sd merged commit e5f7753 into main Sep 26, 2026
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant