Skip to content
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

[3.8.x] Backports #5847

Merged
merged 1 commit into from
Mar 7, 2024
Merged

[3.8.x] Backports #5847

merged 1 commit into from
Mar 7, 2024

Conversation

jamesnetherton
Copy link
Contributor

No description provided.

…ache#5846)

* Bump org.amqphub.quarkus:quarkus-qpid-jms-bom from 2.5.0 to 2.6.0

Bumps [org.amqphub.quarkus:quarkus-qpid-jms-bom](https://github.com/amqphub/quarkus-qpid-jms) from 2.5.0 to 2.6.0.
- [Commits](amqphub/quarkus-qpid-jms@2.5.0...2.6.0)

---
updated-dependencies:
- dependency-name: org.amqphub.quarkus:quarkus-qpid-jms-bom
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

* Auto generated changes for dependabot commit 452db20

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Copy link
Contributor

@zhfeng zhfeng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious. Is there any fix with quarkus-qpid-jms:2.6.0 which we need in 3.8.x?

@jamesnetherton
Copy link
Contributor Author

Just curious. Is there any fix with quarkus-qpid-jms:2.6.0 which we need in 3.8.x?

Not really in this instance. But we should stay aligned with whatever version is used in the platform 3.8.x branch (and elsewhere).

@jamesnetherton jamesnetherton merged commit 0b32ddb into apache:3.8.x Mar 7, 2024
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants