| 18 Sep 2025 |
 emily | I guess that's only relevant on next bump though | 18:44:21 |
 @aloisw:julia0815.de | No, it's already wildly out of date. | 18:44:35 |
| @aloisw:julia0815.de | Lix has 1.0.2, 25.05 has 1.1.0 and unstable has 1.2.0. | 18:45:50 |
| @aloisw:julia0815.de | I can look into bumping (probably to 1.1.0?) this weekend. | 18:46:01 |
| emily | by next bump I mean, the next time the flake bumps | 18:47:41 |
| emily | although I guess the flake deps aren't used with the module. I dunno. I los track of all this | 18:47:53 |
| emily | * although I guess the flake deps aren't used with the module. I dunno. I lost track of all this | 18:47:56 |
| @aloisw:julia0815.de | Please do not worry, I should have subscribed to that PR. In any case due to the staging detour the delay should not cause negative effects. | 18:48:07 |
| emily | I'd pick 1.2.0: https://github.com/capnproto/capnproto/blob/v1.1.0/CMakeLists.txt | 18:48:27 |
| emily | (< 3.5 will not work with CMake 4) | 18:48:38 |
| @aloisw:julia0815.de | Why would "flake bump" matter there? Out of date dependencies are not so great. | 18:48:48 |
| emily | (you could backport more but why bother?) | 18:48:52 |
