On Mi, 10 Mai 2023, Bram Moolenaar wrote:
> Perhaps you can create a PR that reverts 9.0.1536, so we can see when > this works again. I should have thought of that already :facepalm Sure will do soon. > It's strange that the version number goes out of sync, causing CI to > break. I am expecting a new kernel to be released quite soon, which fixes CVE-2023-0386 (https://seclists.org/oss-sec/2023/q2/133) and as such there will probably be a new runner required by Github anyhow. Or maybe this was done already and was a reason for this problem? > Perhaps we should use a different variable to get the version? The way it was used looked good to me. Unfortunately there doesn't seem to pin a github-runner to a specific release/kernel version and as such this may happen occasionally I guess. Best, Christian -- Es ereignet sich nichts Neues. Es sind immer dieselben alten Geschichten, die von immer neuen Menschen erlebt werden. -- William Faulkner -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/ZFuzm3cl3SL4hW/2%40256bit.org.
