Fix deprecation release for azure-mgmg-mixedreality#45405
Closed
MichaelZp0 wants to merge 1 commit intoAzure:mainfrom
Closed
Fix deprecation release for azure-mgmg-mixedreality#45405MichaelZp0 wants to merge 1 commit intoAzure:mainfrom
MichaelZp0 wants to merge 1 commit intoAzure:mainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR attempts to recover from a broken/bad prior release of azure-mgmt-mixedreality by incrementing the package version and adding a corresponding changelog entry so a fresh release can be produced.
Changes:
- Bump package version from
1.1.0b2to1.1.0b3. - Add a
1.1.0b3changelog entry dated 2026-02-26.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| sdk/mixedreality/azure-mgmt-mixedreality/azure/mgmt/mixedreality/_version.py | Updates the package version constant to 1.1.0b3. |
| sdk/mixedreality/azure-mgmt-mixedreality/CHANGELOG.md | Adds release notes for 1.1.0b3. |
|
|
||
| ### Other Changes | ||
|
|
||
| - Fixing error in the last release. |
There was a problem hiding this comment.
The changelog entry is too vague for customers ("Fixing error in the last release"). Please clarify what was wrong in 1.1.0b2 and what this release changes (e.g., republished artifacts/metadata fix, no API/runtime changes) so consumers can understand impact.
Suggested change
| - Fixing error in the last release. | |
| - Republished package to correct packaging/metadata issues introduced in 1.1.0b2. No API surface or runtime behavior changes compared to 1.1.0b2. |
Member
Author
|
I looked at the wrong release PiPy. The 1.1.0b2 packages is released, so no fix is necessary. Abandoning. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There was a mishap in the last release and it might be fixed by just doing a fresh release with all the steps.
I forgot to trigger ./Prepare-Release.ps1 last time before triggering the release pipeline, which now seems to be in a broken state. I am not sure that re-releasing will fix it, but I'd rather try this once than to alert multiple people that have to go through logs and stuff.