Repository navigation
Pin released dependencies and reduce maintenance CI noise - #24
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use released Vulkan v3.2.2, GLFW v2.0.1 and ImGui v0.3.1 / v0.3.1-standard in required desktop/mobile/package lanes. Pin the module manifest to ImGui v0.3.1, whose transitive dependencies match those CI inputs. Preserve advisory master builds, pin Java/Android actions, cancel superseded PR checks and skip duplicate documentation-only pushes.
The source release tags retain each variant's generated/native ABI pairing. Full platform and packaging CI runs on this final graph.
Guided desktop and Android setup now share the ImGui tag declared in v.mod; remove the obsolete IMGUI_REVISION file. Resolve annotated tags to commits when verifying an existing checkout and preserve dirty checkout guards. Enable the existing Linux keyboard-test stack traces if a window-manager startup failure recurs.
Local checks passed on stable V and current V3, including manifest validation, exact-tag acceptance, mismatched-commit rejection, paths with spaces, and preservation of dirty dependency checkouts.
The raw desktop host now waits (at most five seconds, while servicing GLFW events) until its window is visible before the first presentation. Linux CI traces showed Lavapipe blocked in FIFO presentation with an unmapped window. The change passed local Vulkan-validation rendering for all three desktop examples and all six existing shortcut checks using the pinned compiler source/bootstrap and a fresh native library build.