9.0.11
- Bump xmscore to
7.0.12 - Require xmsconan
>=2.18.0(was==2.16.0); pins now float with--upgrade
Packaging
Second library onto the VS2019 bridge, after xmscore 7.0.12. This release's recipe carries the msvc 192 fork, which is the point of the release rather than a side effect.
XmsConan2File.export() copies xms_conan2_file.py into the export folder, so its contents feed the recipe revision hash. xmsconan 2.18.0 changes that file by 192 lines — _is_vs2019(), vs2019_requirements, vs2019_dependency_overrides. Under the old 2.16.0 pin, a 9.0.x built by CI and the same 9.0.x built by the manual VS2019 track would export different recipes and resolve to different recipe revisions, leaving aquaveo-stable and aquaveo-vs2019 silently out of step on what reads as one release.
The xmscore bump is required for the same reason: xms_dependencies pins an exact version, and 7.0.11 was never built for msvc 192. Only 7.0.12 exists on aquaveo-vs2019, so a VS2019 build of xmsgrid pinned to 7.0.11 fails at graph resolution before compiling anything.
Compatibility
No C++ source change since 9.0.10 — the only commit in this release is the dependency and CI bump. The public API and the library sources are identical.
The xmscore bump is inert for the VS2022 builds: 7.0.12's only commit was itself a CI regeneration, so it is the same C++ source as 7.0.11, published on both remotes at recipe revision c58afa49b4625335e8fbaa650c925873.
The dependency graph is otherwise unchanged on every toolchain that is not msvc 192. 2.18.0 refactored the inline self.requires("boost/1.86.0") / self.requires("zlib/1.3.1") calls into an iteration over default_requirements, which holds those same two references in the same order. conanfile.py gains a vs2019_dependency_overrides attribute only when build.toml declares that table, and this repo does not.
Because the recipe revision moves while the sources do not, consumers pinning xmsgrid/9.0.10 are unaffected and can adopt 9.0.11 without rebuilding their own sources.
CI
2.17.0 floated generated CI from == onto >= with --upgrade, so a future xmsconan release reaches CI on its next run instead of requiring a regenerate-and-commit pass. This should be the last "regenerate CI workflows" commit this repo needs. The flake job picks up --upgrade here, which it lacked under the == pin.