Pin Chronos to a Windows-compatible revision for Build Windows CI - #75
Merged
Merged
Conversation
Co-authored-by: Nimaoth <23197842+Nimaoth@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job Build Windows
Pin Chronos to a Windows-compatible revision for Build Windows CI
Sep 18, 2026
Nimaoth
approved these changes
Sep 18, 2026
Nimaoth
marked this pull request as ready for review
September 18, 2026 18:15
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
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.
Build Windowsin Actions failed due to dependency resolution drift: fresh installs selected a newer Chronos revision that no longer compiles with the current Nim nightly (NestedPollundeclared in Chronos async macro path).This change stabilizes CI dependency resolution by pinning Chronos to the last known-good commit used by successful Windows builds.
Dependency pinning
nev.nimbleto use an explicit Chronos commit instead of a floating semver range.Lockfile synchronization
atlas.lockChronos commit to the same pinned revision.atlas.lockto match, keeping both resolution sources aligned.