-
-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove fallback to ~master on dub fetch, fix #2679 #2763
Merged
Merged
Conversation
This file contains 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
✅ PR OK, no changes in deprecations or warnings Total deprecations: 17 Total warnings: 0 Build statistics: statistics (-before, +after)
executable size=5318568 bin/dub
-rough build time=65s
+rough build time=63s Full build output
|
The retry does not make sense, as one cannot add a package to the registry without a release version. It is also not in line with Dub strategy, as we are trying to reduce the usage of branch dependencies. This also fixes issue dlang#2679 which pointed out the error message was sub-par. The API of the registry seems to have changed and we now get `null` instead of `undefined`, leading to an error inside the JSON module instead of the enforce being triggered.
Geod24
force-pushed
the
mlang/masterFallback
branch
from
December 28, 2023 22:48
6524ee1
to
1828307
Compare
Geod24
changed the title
Remove fallback to ~master on dub fetch
Remove fallback to ~master on dub fetch, fix #2679
Dec 28, 2023
Edited to pass CI and fix an issue in the process |
thewilsonator
approved these changes
Dec 28, 2023
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.
The retry does not make sense, as one cannot add a package to the registry without a release version.
It is also not in line with Dub strategy, as we are trying to reduce the usage of branch dependencies.
This also fixes issue #2679 which pointed out the error message
was sub-par. The API of the registry seems to have changed and
we now get
null
instead ofundefined
, leading to an errorinside the JSON module instead of the enforce being triggered.