Downgrade referenceVersion to 3.6.0 and add notes how referenceVersion should be set #21813
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
…imental TASTy version in main. Add notes on how referenceVersion should be tracked
WojciechMazur
force-pushed
the
build/downgradeReferenceVersion
branch
from
b72f84e to
d945d68
Compare
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.
The main branch should always use a compiler with experimental tasty - it's required for non_boostrapped tests to pass. It's required because we cannot consume stable version of tasty from it's experimental subversion (it's assumed that stable version > experimental version for the same major/minor pair)
We pick 3.6.0 (released by mistake during 3.6.0-RC1) because that's the last non-stable version pushed to Maven. Typically we would use the last RC version
[test_non_bootstrapped]