Skip to content

using released version of azure-core for core-amqp #46015

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

anuchandy
Copy link
Member

No description provided.

@Copilot Copilot AI review requested due to automatic review settings July 14, 2025 21:08
@anuchandy anuchandy requested review from conniey, lmolkova and a team as code owners July 14, 2025 21:08
@github-actions github-actions bot added the Azure.Core.AMQP azure-core-amqp label Jul 14, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the azure-core-amqp module to depend on the latest released azure-core version instead of a beta release.

  • Bumps azure-core from 1.56.0-beta.1 to 1.55.5 in the module’s pom.xml.
Comments suppressed due to low confidence (1)

sdk/core/azure-core-amqp/pom.xml:80

  • [nitpick] Consider managing the azure-core version centrally via the parent POM's dependencyManagement section to ensure consistency across modules and avoid having to update individual POMs.
      <version>1.55.5</version> <!-- {x-version-update;com.azure:azure-core;dependency} -->

@alzimmermsft
Copy link
Member

Is this needed to perform a patch release / hotfix release?

If so, you'll want to create a release branch from when azure-core 1.55.5 was released and cherry-pick the fixes made to azure-core-amqp, then release from that branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure.Core.AMQP azure-core-amqp
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants