Skip to content

Increment version for storage releases #51377

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

Merged

Conversation

azure-sdk
Copy link
Collaborator

Increment package version after release of Azure.Storage.DataMovement

@Copilot Copilot AI review requested due to automatic review settings July 21, 2025 20:56
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 increments the package version for Azure.Storage.DataMovement after a release, setting up the project for the next development cycle. The version is updated from 12.2.0 to 12.3.0-beta.1, indicating the start of a new beta release cycle.

  • Updated package version from 12.2.0 to 12.3.0-beta.1
  • Updated API compatibility version from 12.1.0 to 12.2.0
  • Added new changelog entry for the upcoming 12.3.0-beta.1 release

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
Azure.Storage.DataMovement.csproj Updates package version and API compatibility version for next development cycle
CHANGELOG.md Adds new changelog section for 12.3.0-beta.1 with standard template sections

@github-actions github-actions bot added the Storage Storage Service (Queues, Blobs, Files) label Jul 21, 2025
@seanmcc-msft seanmcc-msft merged commit 67e7444 into Azure:main Jul 21, 2025
17 checks passed
@azure-sdk azure-sdk deleted the increment-package-version-storage-5115453 branch July 27, 2025 09:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants