infra: additional testing on core release #30180
Open
+67
−0
Conversation
This file contains 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
dosubot
bot
added
the
size:M
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Here we add a job to the release workflow that, when releasing
langchain-core, tests prior published versions of select packages against the new version of core. We limit the testing to the most recent published versions of langchain-anthropic and langchain-openai.This is designed to catch backward-incompatible updates to core. We sometimes update core and downstream packages simultaneously, so there may not be any commit in the history at which tests would fail. So although core and latest downstream packages could be consistent, we can benefit from testing prior versions of downstream packages against core.
I tested the workflow by simulating a breaking change in core and running it with publishing steps disabled: https://github.com/langchain-ai/langchain/actions/runs/13741876345. The workflow correctly caught the issue.