Update pinecone-plugin-assistant to >=3.0.1 #561
Merged
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
jhamon
changed the title
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.
Problem
The SDK was pinned to
pinecone-plugin-assistant==3.0.0, which prevents automatic updates to compatible patch and minor versions (e.g., 3.0.1, 3.0.2, 3.1.0).Solution
Updated the dependency specification to use a version range (
>=3.0.1,<4.0.0) instead of an exact pin. This allows the SDK to automatically pick up compatible future versions while maintaining API compatibility within the 3.x series.Changes
pyproject.toml: Changedpinecone-plugin-assistant==3.0.0topinecone-plugin-assistant>=3.0.1,<4.0.0uv.lock: Regenerated lock file to resolve to version 3.0.1Impact
Users will automatically receive compatible updates to the assistant plugin (3.0.1, 3.0.2, 3.1.0, etc.) when installing or updating the SDK, without requiring a new SDK release. The version range ensures compatibility within the 3.x major version while preventing breaking changes from 4.0.0+.
Breaking Changes
None. This change maintains backward compatibility and only affects how future compatible versions are resolved.