chore(mergify): update rule to backport to jdk11 branch #384
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
To run smoketest: |
|
No longer needed since #416 |
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.
Since
mainnow depends upon JMC 9, which requires JDK 17+, I have created an upstreamjdk11branch which diverges just before the JMC 9 upgrade was merged. This branch will continue to publish-corereleases in the2.xversion sequence, and will continue to use JMC 8.x and only require JDK 11+. This is useful for the Cryostat Agent, which depends on-corebut only very very loosely on the JMC parts, and for which we want JDK 11 compatibility.