fix: version upgrade - while uploading sample data getting version compatibility error using bash command #720
Conversation
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
Vemarthula-Microsoft
requested review from
Avijit-Microsoft,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft and
aniaroramsft
as code owners
Roopan-Microsoft
approved these changes
Oct 28, 2025
|
🎉 This PR is included in version 1.9.6 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Purpose
This pull request updates the version constraints for the
msalandazure-identityPython packages across multiple requirements files to allow for a wider range of compatible versions while still restricting to major version 1. This improves compatibility and maintainability across different environments.Dependency version updates:
msalto use a version range (>=1.30.0,<2.0.0) instead of a fixed version ininfra/scripts/fabric_scripts/requirements.txtandinfra/scripts/index_scripts/requirements.txt[1] [2]azure-identityto use a version range (>=1.19.0,<2.0.0) instead of a fixed version ininfra/scripts/fabric_scripts/requirements.txt,infra/scripts/index_scripts/requirements.txt, andsrc/App/requirements.txt[1] [2] [3]Dependency management cleanup:
[broker]extra from themsaldependency ininfra/scripts/index_scripts/requirements.txtto standardize the dependency specificationDoes this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information