fix: pin langfuse image to version 2 #18
Merged
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
bzadon
approved these changes
Dec 9, 2024
|
Thank you, merging! |
Downgrading Langfuse from V3 to V2For anyone experiencing this issue due to the automigration of Langfuse to the latest version (V3):
Step by step to downgrade the last version V2: |
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.
What
@pamelafox: After creating our v3 milestone, we got the feedback that the Azure sample is breaking due to new mandatory environment variables. If we pin the image to
:2that can be avoided until this sample starts to support v3.