chore: Added upper version bounds to dependencies in "pyproject.toml" #2486
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
fcc07fb to
92ed6f8
Compare
This change keeps dependencies to their major versions, but for the pre 1.0.0 releases pinned to minor releases as they could have breaking changes. PyYAML: Version 7.0 is in development and could have breaking changes absolufy-imports: The package is archived and no longer maintained. anyio: Follows SemVer, so version 5.0 could have breaking changes. authlib: Follows a SemVer-like pattern, so version 2.0 could have breaking changes. click: A mature library, version 9.0 is the expected boundary for breaking changes. fastapi: As a pre-1.0 library, the next minor release could have breaking changes. google-api-python-client: Although in maintenance, version 3.0 could still have breaking changes. google-cloud-aiplatform: Follows SemVer, so breaking changes are expected in version 2.0. google-cloud-secret-manager: A stable Google library, version 3.0 could lead to breaking changes. google-cloud-speech: A stable Google library, version 3.0 could lead to breaking changes. google-cloud-storage: A stable Google library. google-genai: As an official Google SDK, version 2.0 is the expected boundary for breaking changes. graphviz: As a pre-1.0 library, the next minor release could have breaking changes. mcp: As an SDK, version 2.0 is the boundary for potential breaking changes. opentelemetry-api: Follows SemVer; version 2.0 could have breaking changes. opentelemetry-exporter-gcp-trace: It's tied to the v1 OpenTelemetry API, so version 2.0 would likely be a breaking change. opentelemetry-sdk: It's coupled to the v1 API, so version 2.0 would likely be a breaking change. pydantic: This stops upgrades to the incompatible version 3.0 after its major 2.0 rewrite. python-dateutil: Follows to SemVer, making version 3.0 the boundary for potential breaking changes. python-dotenv: Locks to stable version 1.0 major release. requests: As a more mature library, version 3.0 is boundary for breaking changes. sqlalchemy: This locks the dependency to the stable version 2.0 API after its major rewrite. starlette: As a pre-1.0 library, the next minor release could have breaking changes. tenacity: This is a mature library, version 9.0 is boundary for breaking changes. typing-extensions: Major versions are tied to large typing changes in Python itself. tzlocal: The library has a history of introducing breaking API changes between major versions. uvicorn: As a pre-1.0 library, the next minor release could have breaking changes. watchdog: As a stable library, version 7.0 could have breaking changes. websockets: Follows SemVer, so version 16.0 is the boundary for breaking changes. PiperOrigin-RevId: 794677571
92ed6f8 to
a74d334
Compare
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.
chore: Added upper version bounds to dependencies in "pyproject.toml"
This change keeps dependencies to their major versions, but for the pre 1.0.0 releases pinned to minor releases as they could have breaking changes.
PyYAML: Version 7.0 is in development and could have breaking changes
absolufy-imports: The package is archived and no longer maintained.
anyio: Follows SemVer, so version 5.0 could have breaking changes.
authlib: Follows a SemVer-like pattern, so version 2.0 could have breaking changes.
click: A mature library, version 9.0 is the expected boundary for breaking changes.
fastapi: As a pre-1.0 library, the next minor release could have breaking changes.
google-api-python-client: Although in maintenance, version 3.0 could still have breaking changes.
google-cloud-aiplatform: Follows SemVer, so breaking changes are expected in version 2.0.
google-cloud-secret-manager: A stable Google library, version 3.0 could lead to breaking changes.
google-cloud-speech: A stable Google library, version 3.0 could lead to breaking changes.
google-cloud-storage: A stable Google library.
google-genai: As an official Google SDK, version 2.0 is the expected boundary for breaking changes.
graphviz: As a pre-1.0 library, the next minor release could have breaking changes.
mcp: As an SDK, version 2.0 is the boundary for potential breaking changes.
opentelemetry-api: Follows SemVer; version 2.0 could have breaking changes.
opentelemetry-exporter-gcp-trace: It's tied to the v1 OpenTelemetry API, so version 2.0 would likely be a breaking change.
opentelemetry-sdk: It's coupled to the v1 API, so version 2.0 would likely be a breaking change.
pydantic: This stops upgrades to the incompatible version 3.0 after its major 2.0 rewrite.
python-dateutil: Follows to SemVer, making version 3.0 the boundary for potential breaking changes.
python-dotenv: Locks to stable version 1.0 major release.
requests: As a more mature library, version 3.0 is boundary for breaking changes.
sqlalchemy: This locks the dependency to the stable version 2.0 API after its major rewrite.
starlette: As a pre-1.0 library, the next minor release could have breaking changes.
tenacity: This is a mature library, version 9.0 is boundary for breaking changes.
typing-extensions: Major versions are tied to large typing changes in Python itself.
tzlocal: The library has a history of introducing breaking API changes between major versions.
uvicorn: As a pre-1.0 library, the next minor release could have breaking changes.
watchdog: As a stable library, version 7.0 could have breaking changes.
websockets: Follows SemVer, so version 16.0 is the boundary for breaking changes.