[ext/HSG]: Store next release _and_ latest nightly #2418
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
|
This should be merged after #2417 |
|
@staticfloat Can you resolve the merge conflicts? Alternatively, since I just merged #2417 to master, it might be easier for you to just redo this commit from scratch starting with the latest master. |
In the event that we are in an RC phase where we have three "latest" branch tips (e.g. latest stable: 1.5.3, latest RC: 1.6.0-rc1 and latest `master`: 1.7.0-DEV) each with their own set of standard libraries, we must store this information in Pkg so that we pass tests when running on latest `master`. It is harmless for this information to be baked into an older Julia, as we make no guarantees that Julia 1.6.0 final should have perfect information about what standard libraries 1.7.0 will have.
|
Yeah, it's because it bundled the commit you just merged. Silly |
staticfloat
force-pushed
the
sf/nightly_stdlibs
branch
from
d9c255a to
f4aed5d
Compare
Classic Git. |
I guess this is the kind of thing that Pijul is supposed to solve. |
KristofferC
pushed a commit
that referenced
this pull request
Mar 2, 2021
In the event that we are in an RC phase where we have three "latest" branch tips (e.g. latest stable: 1.5.3, latest RC: 1.6.0-rc1 and latest `master`: 1.7.0-DEV) each with their own set of standard libraries, we must store this information in Pkg so that we pass tests when running on latest `master`. It is harmless for this information to be baked into an older Julia, as we make no guarantees that Julia 1.6.0 final should have perfect information about what standard libraries 1.7.0 will have. (cherry picked from commit 7a9d965)
KristofferC
pushed a commit
that referenced
this pull request
Mar 2, 2021
In the event that we are in an RC phase where we have three "latest" branch tips (e.g. latest stable: 1.5.3, latest RC: 1.6.0-rc1 and latest `master`: 1.7.0-DEV) each with their own set of standard libraries, we must store this information in Pkg so that we pass tests when running on latest `master`. It is harmless for this information to be baked into an older Julia, as we make no guarantees that Julia 1.6.0 final should have perfect information about what standard libraries 1.7.0 will have. (cherry picked from commit 7a9d965)
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.
In the event that we are in an RC phase where we have three "latest"
branch tips (e.g. latest stable: 1.5.3, latest RC: 1.6.0-rc1 and latest
master: 1.7.0-DEV) each with their own set of standard libraries, wemust store this information in Pkg so that we pass tests when running on
latest
master. It is harmless for this information to be baked into anolder Julia, as we make no guarantees that Julia 1.6.0 final should have
perfect information about what standard libraries 1.7.0 will have.
Fixes #2410