-
Notifications
You must be signed in to change notification settings - Fork 16
Merge eap
branch back into main
#171
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
Conversation
fioan89
commented
Feb 28, 2023
- main branch will now support Gateway 2022.3 versions
- major version changed because of Gateway API is incompatible with older versions - eap is now the release channel.
- I think it's better for MAJOR.MINOR.PATCH to be synchronized with main branch. - the first three versions will change when business will change while `eap-x` will be increased when support for new Gateway releases is added
- release channels other than default one have to be configured by users the Jetbrains products which is a bit inconvenient. - as long as the Gateway supported versions don't overlap with main branch then it's safe to release in the main channel.
Changelog update - `v2.1.2-eap.0`
- include all bugfixes and enhancements released with `2.1.3`
Changelog update - `v2.1.3-eap.0`
Changelog update - `v2.1.4-eap.0`
Changelog update - `v2.1.5-eap.0`
Changelog update - `v2.1.6-eap.0`
- main branch will now provide support for Gateway 2022.3 and onwards
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of curiosity, what made the build break if no source-code changes needed to be made?
@kylecarbs there were a couple of explicit API calls that were not compatible with Gateway 2022.2, but I got rid of them two months ago with this rework: 0b5a256#diff-2181dc554d6743aadbfd2d3a9399b635536069a24e647fc82c98cdfa4fbf2bfa There are however a couple of other things that make the SDK of Gateway 2022.2 and Gateway 2022.3 incompatible:
|