Update versions to 4.3.3 - #14
Merged
Merged
Conversation
LoisSotoLopez
marked this pull request as ready for review
July 31, 2026 09:34
the-mikedavis
left a comment
There was a problem hiding this comment.
I see a mix of 4.3.3 and 4.3.4 in the diff - probably 4.3.4 would suffice for all 4.3.3 references given how closely together they were released?
Author
Maybe it would be better to just update versions to 4.3.3. |
Member
|
It seems to be that the nomenclature for community plugin versioning is that |
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
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.
Proposed Changes
4.3.3 bumped minimum otp verson to 27.
As reported in #13 we need to adapt.
Bumped OTP version in multiple places,
started testing with erlang 29 too keep testing with 3 Erlang versions, kept thebroker_version_requirementsconfigured to 4.3.3 even though RABBITMQ_VERSION is 4.3.4.Further Comments