Skip to content

Release new GA version of Azure.Core that uses 1.4.0 #49556

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

Closed
Tracked by #48292
m-nash opened this issue Apr 22, 2025 · 1 comment · Fixed by #49848
Closed
Tracked by #48292

Release new GA version of Azure.Core that uses 1.4.0 #49556

m-nash opened this issue Apr 22, 2025 · 1 comment · Fixed by #49848
Assignees
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library.

Comments

@m-nash
Copy link
Member

m-nash commented Apr 22, 2025

Update azure core and shared source to use the new SCM and analyzer build from #48292

@m-nash m-nash self-assigned this Apr 22, 2025
@m-nash m-nash added Client This issue points to a problem in the data-plane of the library. Azure.Core labels Apr 22, 2025
@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Apr 22, 2025
Copy link

Hi @m-nash, I'm an AI Support assistant here to help with your issue. While the Azure SDK team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

  • Verify that breaking changes (e.g. removal of AuthenticationRecord, AuthenticationRequiredException, and modifications to credential options) have been thoroughly communicated and documented (see Azure.Identity CHANGELOG).
  • Ensure that downstream clients or libraries updated to Azure.Core 1.4.0 have been tested against these breaking changes.
  • Confirm that all dependency upgrades (for example, those in other client libraries such as Communication or ResourceManager packages) correctly reference Azure.Core 1.4.0 and are compatible with the GA release.
  • Validate that release notes clearly indicate no accidental removals or modifications beyond what is planned, matching the expectations set in the beta versions.

The Azure SDK team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

@jsquire jsquire removed the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library.
Projects
None yet
3 participants