EGC v1.1.18 released - Windows install fixed at the root, and an apology

[Fmarzochi]

v1.1.16 shipped broken in two ways, and both are on me.

First, the changelog and roadmap for that release only documented 2 of the roughly 25 pull requests that actually went into it — the entire overnight batch of fixes was missing. I caught it after a bot flagged a chronology error, not before shipping. That's backwards. It was fixed retroactively in #1044, and the v1.1.16 docs now match what was actually released.

Second, and worse: install.ps1, the Windows installer, had drifted out of sync with install.sh for several releases — the wrong Node version floor, no lockfile-aware dependency install, and a bug that could silently overwrite a user's existing MCP config if it failed to parse. Underneath all of that was a deeper bug: install.sh itself was writing Git Bash's POSIX-style paths (/c/Users/...) into MCP config files that native Windows apps can't read. That's the real reason Windows installs have been unreliable, and it should have been caught a long time ago.

v1.1.17 fixes the actual root cause, not just the symptom. install.sh now detects Git Bash/MSYS and writes Windows-native paths. install.ps1 is back in sync with install.sh, feature for feature. And this time, before merging, I ran the full Windows CI matrix (Node 20 and 22, across npm/yarn/bun) and watched all of it pass, instead of assuming it would.

If you tried to install EGC on Windows recently and it didn't work, or noticed the v1.1.16 changelog looked thin, that was real, and it was on us. Sorry — genuinely. Upgrade to v1.1.17 and it should be fixed. If it isn't, open an issue and I'll treat it as priority.

Full changelog: https://github.com/Fmarzochi/EGC/blob/main/CHANGELOG.md#1117---2026-07-27
Release: https://github.com/Fmarzochi/EGC/releases/tag/v1.1.17

— Felipe