fix: gui CI after closure lifetime merge#3
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 70251d7613
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
70251d7 to
17af549
Compare
|
@codex review |
|
Codex Review: Didn't find any major issues. Breezy! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
ad45ece to
fa702d2
Compare
fa702d2 to
47bed52
Compare
Summary
This updates the v-gui CI after the closure lifetime/reclaim work landed in V.
The Windows job was still pinned to V
0.5.1, which does not include the new closure lifetime/reclaim API used by v-gui. This switches the Windows job tovlang/setup-vwith the latest V compiler, matching the other CI jobs more closely.It also refreshes the Windows dependency cache keys from the installed V version, so compiler updates do not keep reusing stale V/vglyph-related caches.
Changes
vlang/setup-v@v1.4for the Windows CI job.vcpkgandvglyphcaches from the installed V version.examples/showcase.vso the CI format check passes.Notes
This PR does not change the closure lifetime/reclaim behavior itself.
macOS still depends on the separate vglyph fix, because the current failure there comes from compiling vglyph as a dependency with newer V checks.
Tests