-
Notifications
You must be signed in to change notification settings - Fork 212
clarify behavior around prereleases in langsmith deployments #966
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR clarifies the behavior of prerelease versions in LangSmith deployments by documenting how uv
/pip
handle prereleases by default and providing instructions for enabling them.
Key Changes:
- Added documentation explaining that prereleases are not installed by default, following
uv
/pip
conventions - Provided two methods for allowing prereleases: configuration in
pyproject.toml
or explicit version specification in other dependency files
Preview ID generated: preview-isaacp-1760664920-7e2e1c0 |
Co-authored-by: Copilot <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
Preview ID generated: preview-isaacp-1760665961-e3756ab |
Preview ID generated: preview-isaacp-1760706732-d563a0d |
@isahers1 I edited your content slightly and added it to a snippet so it could be included on multiple pages. There may be more places that this tip could be useful, but for now just added to the pyproject and requirements.txt pages. |
No description provided.