feat: version 3.13 replaces version 3.11 #259
Closed
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.
Description
3.11 has been removed and replaced with 3.13. Updates to the validation and tests to retain min/max version constraints.
https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-versioning-policy shows that 3.12 is next to EOL. No mention of 3.11.
Release required?
x.x.X)x.X.x)X.x.x)Release notes content
End of life for IBM Cloud Databases RabbitMQ version 3.11.
Added 3.13 (which is the preferred version) so that it can be locked by consuming modules.
Upgrade documentation: https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-upgrading&interface=ui
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers