Skip to content

Conversation

@kshitij-microsoft
Copy link
Member

@kshitij-microsoft kshitij-microsoft commented Mar 4, 2025

Description

Pinned the major versions of external dependencies. the current version of the dependency is mentioned below alongwith whether it is an internal dependency:
"pyyaml>=5.1.0, < 7", // 6.0.2
"msrest>=0.6.18", // 0.7.1
"azure-core>=1.23.0", // 1.32.0 / internal
"azure-mgmt-core>=1.3.0", // 1.5.0 / internal
"marshmallow>=3.5, < 4", // 3.26.1
"jsonschema>=4.0.0, < 5", // 4.23.0
"tqdm < 5", // 4.67.1
"strictyaml < 2", // 1.7.3
"colorama", // 0.4.6
"pyjwt < 3", // 2.10.1
"azure-storage-blob>=12.10.0", // 12.24.1 / internal
"azure-storage-file-share", // 12.20.1 / internal
"azure-storage-file-datalake>=12.2.0", // 12.18.1 / internal
"pydash>=6.0.0, < 9", // 8.0.5
"isodate", // 0.7.2
"azure-common>=1.1 , < 2", // 1.1.28 / internal
"typing-extensions < 5", // 4.12.2
"azure-monitor-opentelemetry", // 1.6.5 / internal
Also, the dependencies with version less than 1 are not pinned since they are also considered as experimental and 1 should be treated as a stable version.

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants