# Ann: SWI-Prolog 9.2.0 (stable) and 9.3.0 (new devel series) **URL:** \ **Category:** Releases\ **Created:** [February 1, 2024, 9:05am UTC](https://swi-prolog.discourse.group/t/ann-swi-prolog-9-2-0-stable-and-9-3-0-new-devel-series/7214 "2024-02-01T09:05:34Z")\ **Posts on this page:** 1\ **Showing post:** 12
**Author:** ![mgondan1](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/mgondan1/32/803_2.png) [@mgondan1](https://swi-prolog.discourse.group/u/mgondan1)\ **Post date:** [February 2, 2024, 4:06pm UTC](https://swi-prolog.discourse.group/t/ann-swi-prolog-9-2-0-stable-and-9-3-0-new-devel-series/7214/12 "2024-02-02T16:06:47Z")
It actually works fine within the CI system of [MSYS2 · GitHub](http://github.com/msys2). Maybe my local installation is broken. Is this still relevant? > [@Testing msys2 build](https://swi-prolog.discourse.group/t/testing-msys2-build/7009): > > I think for @mgondan1. I’ve pushed a lot of changes to the cmake scripts, notably affecting Windows. The aim is to make the sources build cleanly under Conda. Some of this also interferes with the MSYS2 port. Notably, rather than creating a shell script for the public binaries by lack of symbolic links, it now installs swipl.exe, etc into the public binary directory. The public binary contains a relative path to the Prolog home. These changes are likely to break the MSYS2 port. If … My gut feeling says no. --- _[View the full topic](https://swi-prolog.discourse.group/t/ann-swi-prolog-9-2-0-stable-and-9-3-0-new-devel-series/7214)._