Thomas Eizinger

> I just saw this discussion and the GitHub announcement, which explains the situation. [news.ycombinator.com/item?id=43936992](https://news.ycombinator.com/item?id=43936992) > > Some users commented that GitHub might have started rolling out the change before...

This would be amazing! I've just started using `render` and the fact that you have to quote every string is a bit annoying because it causes quite a bit of...

This is affecting windows-2025 now as well: https://github.com/firezone/firezone/actions/runs/15789902409/job/44513762369

Interestingly, this only appears to affect one particular workflow of ours. Other Windows workflows where we build Rust code work fine.

This is not the job that is failing. The job that is failing is: https://github.com/firezone/firezone/actions/runs/15816630435/job/44576867194 It appears to be a regression in the Microsoft compiler shipped with the new Visual...

As a workaround, we are now using `lld` as suggested in https://github.com/rust-lang/rust/issues/141626#issuecomment-2919988483. No issues so far but we still need to do further testing on the produced binaries.

> Could this flag be set in the runner, so not every project has to experience a failure, search for the solution, then set the flag, then unset it later...

> [@thomaseizinger](https://github.com/thomaseizinger) I hope your issue got resolved after adding the `linker = "rust-lld"`. Could you please confirm on this.Thank you. Well, it is a workaround. The default linker shipped...

I am not sure what you mean by "syncing the main branch". I tried running a build of our software with the standard linker that comes with the latest Windows...

The above run uses the latest windows-2025 image: https://github.com/actions/runner-images/releases/tag/win25%2F20250708.1