Open
Conversation
Member
|
So ... you want to update regardless? Are these issues pre-existing? |
Collaborator
Author
|
I'm not sure regarding "regardless" what you mean? The regression I want to fix has been introduced since #25537 (March 7, 2026) and it breaks CI that use nim-nightlies. The difference between the current 0.22.2 and 0.23.3 is pretty small so should be safe: nim-lang/nimble@v0.22.2...v0.22.3 Basically what is missing is this |
Member
|
Yeah, I had the same problem when I worked on nimedit CI. |
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
3 participants
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.
The task-level exit code issue that is apparently fixed has been plaguing me.
Also resolving path override and trying to download nimble with nimble in CI is a pain: mratsim/constantine#602 (comment)
Release: https://github.com/nim-lang/nimble/releases/tag/v0.22.3