chore(deps): various minor and patch version updates #597
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
![ellipsis-dev[bot]](https://avatars.githubusercontent.com/in/64358?s=60&v=4){kind=small}
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed everything up to b62e5df in 1 minute and 44 seconds. Click for details.
- Reviewed
485lines of code in15files - Skipped
1files when reviewing. - Skipped posting
50draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. package.json:11
- Draft comment:
Consistent dependency bump; verify that all new versions (e.g. @commitlint, eslint, nx) don’t break expected behavior. - Reason this comment was not posted:
Confidence changes required:50%<= threshold50%None
2. packages/instrumentation-anthropic/package.json:48
- Draft comment:
Update to @anthropic-ai/sdk (^0.39.0) appears valid; check for any breaking changes in the new version. - Reason this comment was not posted:
Confidence changes required:30%<= threshold50%None
3. packages/instrumentation-azure/package.json:41
- Draft comment:
Opentelemetry packages updated to ^1.30.1 & ^0.200.0; ensure compatibility with Azure integration. - Reason this comment was not posted:
Confidence changes required:30%<= threshold50%None
4. packages/instrumentation-bedrock/package.json:48
- Draft comment:
AWS SDK client update to ^3.787.0; confirm that no API changes affect bedrock integration. - Reason this comment was not posted:
Confidence changes required:30%<= threshold50%None
5. packages/instrumentation-chromadb/package.json:51
- Draft comment:
Chromadb version bumped to ^1.10.5; check that the new version is backward compatible. - Reason this comment was not posted:
Confidence changes required:30%<= threshold50%None
6. packages/instrumentation-cohere/package.json:51
- Draft comment:
Cohere-ai version upgraded to ^7.17.1; verify API compatibility. - Reason this comment was not posted:
Confidence changes required:30%<= threshold50%None
7. packages/instrumentation-langchain/package.json:48
- Draft comment:
Langchain packages updated (community and openai); ensure integration tests cover any changes. - Reason this comment was not posted:
Confidence changes required:40%<= threshold50%None
8. packages/instrumentation-llamaindex/package.json:52
- Draft comment:
llamaindex bumped to ^0.10.2; confirm that API changes (if any) are handled. - Reason this comment was not posted:
Confidence changes required:40%<= threshold50%None
9. packages/instrumentation-openai/package.json:54
- Draft comment:
openai and js-tiktoken versions updated; please verify the integration with OpenAI SDKs. - Reason this comment was not posted:
Confidence changes required:40%<= threshold50%None
10. packages/instrumentation-pinecone/package.json:41
- Draft comment:
Opentelemetry deps updated; integration with Pinecone remains unchanged. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
11. packages/instrumentation-qdrant/package.json:47
- Draft comment:
qdrant client updated to ^1.14.0; verify if any breaking changes affect Qdrant integration. - Reason this comment was not posted:
Confidence changes required:30%<= threshold50%None
12. packages/instrumentation-together/package.json:53
- Draft comment:
together-ai updated to ^0.15.1 and js-tiktoken to ^1.0.20; please ensure functionality remains intact. - Reason this comment was not posted:
Confidence changes required:30%<= threshold50%None
13. packages/instrumentation-vertexai/package.json:47
- Draft comment:
VertexAI instrumentation: google-cloud deps bumped; check Vertex AI integration after update. - Reason this comment was not posted:
Confidence changes required:30%<= threshold50%None
14. packages/sample-app/package.json:40
- Draft comment:
Sample app dependencies updated consistently; ensure sample scripts work with new versions. - Reason this comment was not posted:
Confidence changes required:30%<= threshold50%None
15. packages/traceloop-sdk/package.json:38
- Draft comment:
Traceloop SDK dependency updates propagate new versions; run integration tests to catch any regressions. - Reason this comment was not posted:
Confidence changes required:40%<= threshold50%None
16. package.json:11
- Draft comment:
Updated devDependencies versions. Verify tool compatibility. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
17. packages/instrumentation-anthropic/package.json:41
- Draft comment:
Bumped opentelemetry and SDK versions; test integration. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
18. packages/instrumentation-azure/package.json:41
- Draft comment:
Updated opentelemetry packages; confirm service alignment. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
19. packages/instrumentation-bedrock/package.json:41
- Draft comment:
Upgraded opentelemetry and AWS SDK client version; check AWS integration. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
20. packages/instrumentation-chromadb/package.json:41
- Draft comment:
Upgrade Chromadb dependency to ^1.10.5. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
21. packages/instrumentation-cohere/package.json:48
- Draft comment:
Increment cohere-ai version to ^7.17.1. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
22. packages/instrumentation-langchain/package.json:48
- Draft comment:
Bumped Langchain-related dependencies; verify no breaking changes. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
23. packages/instrumentation-llamaindex/package.json:49
- Draft comment:
Bumped llamaindex version to ^0.10.2. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
24. packages/instrumentation-openai/package.json:40
- Draft comment:
Updated openai and js-tiktoken dependencies; ensure API changes are handled. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
25. packages/instrumentation-pinecone/package.json:38
- Draft comment:
Minor opentelemetry updates; no apparent issues. - Reason this comment was not posted:
Confidence changes required:10%<= threshold50%None
26. packages/instrumentation-qdrant/package.json:40
- Draft comment:
Updated @qdrant/js-client-rest to ^1.14.0. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
27. packages/instrumentation-together/package.json:40
- Draft comment:
Bump together-ai to ^0.15.1; verify overall integration. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
28. packages/instrumentation-vertexai/package.json:40
- Draft comment:
Upgrade opentelemetry and Google Cloud VertexAI dependencies. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
29. packages/sample-app/package.json:37
- Draft comment:
Synchronized sample-app dependency versions to match SDK updates. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
30. packages/traceloop-sdk/package.json:37
- Draft comment:
Updated SDK dependencies; ensure compatibility with instrumentation packages. - Reason this comment was not posted:
Confidence changes required:20%<= threshold50%None
31. package.json:2
- Draft comment:
The project name "openllmetry-js" looks like it might be misspelled. If the intended name is "opentelemetry-js", please update it to avoid confusion. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
32. package.json:7
- Draft comment:
The script key "build:effected" in package.json might be a typographical error. If it is intended to trigger the build process for affected projects, consider renaming it to "build:affected" to improve clarity. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
33. packages/instrumentation-anthropic/package.json:4
- Draft comment:
Typo found in the "description" field: 'Anthropic Instrumentaion' should be 'Anthropic Instrumentation'. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
34. packages/instrumentation-azure/package.json:4
- Draft comment:
Typo detected in the 'description' field: 'Azure OpenAI Instrumentaion'. Consider correcting it to 'Azure OpenAI Instrumentation'. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
35. packages/instrumentation-bedrock/package.json:22
- Draft comment:
Typo: The 'author' field is formatted as 'Swaroopmaddisaiswaroop@gmail.com'. Consider adding a space between the name and the email (e.g., 'Swaroop maddisaiswaroop@gmail.com') for better readability. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
36. packages/instrumentation-bedrock/package.json:53
- Draft comment:
Typo: The 'homepage' URL in line 53 references 'instrumentation-openai' while the package name is '@traceloop/instrumentation-bedrock'. Please update the URL to correctly refer to the 'instrumentation-bedrock' package. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
37. packages/instrumentation-chromadb/package.json:22
- Draft comment:
Typographical error: Consider adding a space between the name and the email in the author field. For example, change "Swaroopmaddisaiswaroop@gmail.com" to "Swaroop maddisaiswaroop@gmail.com". - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
38. packages/instrumentation-cohere/package.json:8
- Draft comment:
Typographical error: The repository field value 'openllmetry-js' appears to be misspelled. It is likely intended to be 'opentelemetry-js'. Please verify and correct if necessary. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
39. packages/instrumentation-cohere/package.json:22
- Draft comment:
Typographical issue: In the author field, 'Swaroopmaddisaiswaroop@gmail.com' should include a space between the name and the email address (e.g., 'Swaroop maddisaiswaroop@gmail.com'). - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
40. packages/instrumentation-cohere/package.json:53
- Draft comment:
Typographical/Reference error: The 'homepage' field currently points to the 'instrumentation-openai' package ('https://github.com/traceloop/openllmetry-js/tree/main/packages/instrumentation-openai') which seems inconsistent with the 'instrumentation-cohere' package. Please review and update the link if it should reference 'instrumentation-cohere' instead. - Reason this comment was not posted:
Comment was on unchanged code.
41. packages/instrumentation-langchain/package.json:8
- Draft comment:
Typo detected: The repository field value "traceloop/openllmetry-js" appears to be misspelled. Consider correcting it to "traceloop/opentelemetry-js" if that is the intended repository name. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
42. packages/instrumentation-openai/package.json:4
- Draft comment:
Typo found in the description field: "OpenAI Instrumentaion". Please correct it to "OpenAI Instrumentation". - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
43. packages/instrumentation-pinecone/package.json:22
- Draft comment:
Typographical Error: The author field "Kartikaykartikaybagla@gmail.com" is missing a space between the name and the email address. Consider changing it to "Kartikay kartikaybagla@gmail.com" for improved readability. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
44. packages/instrumentation-qdrant/package.json:8
- Draft comment:
Typographical error: The repository name in the "repository" field is currently "traceloop/openllmetry-js". Consider revising it to "traceloop/opentelemetry-js" if that was the intended spelling. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
45. packages/instrumentation-together/package.json:56
- Draft comment:
It looks like the homepage URL (https://github.com/traceloop/openllmetry-js/tree/main/packages/instrumentation-openai) refers to the instrumentation-openai package. Since this package is @traceloop/instrumentation-together, please update the homepage URL to point to the correct repository or package directory. - Reason this comment was not posted:
Comment was on unchanged code.
46. packages/instrumentation-vertexai/package.json:8
- Draft comment:
Typographical error: The repository field value "traceloop/openllmetry-js" appears to have a typo. Consider correcting it to "traceloop/opentelemetry-js" if that's what was intended. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
47. packages/instrumentation-vertexai/package.json:21
- Draft comment:
Typographical formatting issue: In the author field, "Swaroopmaddisaiswaroop@gmail.com", there is no space between the name and the email. Consider formatting it as "Swaroop maddisaiswaroop@gmail.com". - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
48. packages/instrumentation-vertexai/package.json:50
- Draft comment:
Typographical error in the homepage URL: it points to ".../instrumentation-openai" while the package is for VertexAI. It likely should be updated to "instrumentation-vertexai" to reflect the correct package name. - Reason this comment was not posted:
Comment was on unchanged code.
49. packages/traceloop-sdk/package.json:8
- Draft comment:
Typo found in the repository field: 'openllmetry-js' might be a misspelling of 'opentelemetry-js'. Please verify and correct if needed. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
50. packages/traceloop-sdk/package.json:61
- Draft comment:
Typo found in the homepage URL: 'openllmetry-js' appears to be misspelled. Consider updating it to 'opentelemetry-js' if that is the intended repository name. - Reason this comment was not posted:
Comment was on unchanged code.
Workflow ID: wflow_1mMS19Ki1IARirrB
You can customize 
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed a49598e in 2 minutes and 16 seconds. Click for details.
- Reviewed
719lines of code in18files - Skipped
0files when reviewing. - Skipped posting
18draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. packages/instrumentation-langchain/test/instrumentation.test.ts:78
- Draft comment:
Avoid reassigning imported identifiers like PromptTemplate. Consider importing it explicitly rather than reassigning from mod.PromptTemplate. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50% The comment is technically correct - reassigning imported identifiers is generally not a good practice. However, this is in a test file and appears to be part of test setup. The reassignment seems intentional to handle dynamic imports needed for the test environment. The original import on line 30 and this reassignment may serve different purposes in the test setup. I could be wrong about the necessity of this dynamic import pattern - maybe there's a cleaner way to structure the test setup. The comment might be pointing out a legitimate code quality issue. While the comment identifies a real code style issue, this appears to be intentional test setup code where normal code style rules may not fully apply. The dynamic import pattern may be necessary for proper test isolation. This comment should be deleted as it's questioning an intentional test setup pattern that, while not ideal style-wise, appears to serve a specific testing purpose.
2. packages/instrumentation-pinecone/test/instrumentation.test.ts:85
- Draft comment:
Avoid shadowing the outer variable 'pc_index' by redeclaring it within the if block. - Reason this comment was not posted:
Comment was on unchanged code.
3. packages/instrumentation-azure/test/instrumentation.test.ts:63
- Draft comment:
Ensure environment variables like AZURE_RESOURCE_NAME, AZURE_API_KEY, and AZURE_DEPLOYMENT_ID are securely managed; using hardcoded test-key is acceptable for tests but consider clarifying usage. - Reason this comment was not posted:
Confidence changes required:50%<= threshold50%None
4. packages/instrumentation-together/test/instrumentation.test.ts:62
- Draft comment:
Passing { enrichTokens: true } to TogetherInstrumentation is fine, but ensure that token enrichment doesn't expose sensitive data in non-test environments. - Reason this comment was not posted:
Comment was on unchanged code.
5. packages/instrumentation-qdrant/tests/instrumentation.test.ts:54
- Draft comment:
Ensure that the testing URL and API key for Qdrant use secure or dummy values to prevent accidental exposure in production. - Reason this comment was not posted:
Confidence changes required:50%<= threshold50%None
6. packages/instrumentation-vertexai/tests/gemini.test.ts:30
- Draft comment:
The test is skipped; if intentionally disabled, add a comment explaining why it is skipped. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%The comment is asking the PR author to add an explanation for a skipped test, which is similar to asking for confirmation or explanation. This violates the rule against asking the author to confirm their intention or explain their actions.
7. packages/instrumentation-vertexai/tests/palm2.test.ts:31
- Draft comment:
The test is also skipped; consider annotating the reason for skipping these tests, so future maintainers know if they should be enabled or how to run them. - Reason this comment was not posted:
Comment was on unchanged code.
8. packages/instrumentation-openai/test/instrumentation.test.ts:68
- Draft comment:
Consider handling potential errors when instantiating the OpenAI client; tests assume successful instantiation. - Reason this comment was not posted:
Confidence changes required:50%<= threshold50%None
9. packages/instrumentation-vertexai/tests/palm2.test.ts:30
- Draft comment:
The test suite is marked with describe.skip. If these tests are intended to run in CI eventually, please add a comment/TODO explaining why they are skipped. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%The comment is asking the author to add a comment or TODO explaining why tests are skipped. This is a request for additional information, which violates the rule against asking the author to update the PR description or provide explanations.
10. packages/instrumentation-vertexai/tests/palm2.test.ts:41
- Draft comment:
Mixing require with ES modules may lead to inconsistencies. Consider using dynamic import consistently for loading '@google-cloud/vertexai'. - Reason this comment was not posted:
Comment was on unchanged code.
11. packages/instrumentation-vertexai/tests/palm2.test.ts:55
- Draft comment:
Environment variables (e.g. VERTEXAI_PROJECT_ID, VERTEXAI_LOCATION) are accessed with the nullish operator. Consider adding validation to ensure they are defined to avoid silent failures in CI. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
12. packages/instrumentation-vertexai/tests/palm2.test.ts:87
- Draft comment:
The assertion comparing the span attribute 'gen_ai.completion.0.content' with the full text response is very strict. Consider adding error handling or a fallback in case the response content is missing or empty. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
13. packages/instrumentation-vertexai/tests/palm2.test.ts:111
- Draft comment:
In the Chat prompt test, ensure that the nested extraction of the 'fullTextResponse' field from the complex response structure is robust against API changes. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
14. packages/instrumentation-azure/test/instrumentation.test.ts:63
- Draft comment:
Typo noticed: The environment variable AZURE_DEPLOYMENT_ID is set to "openllmetry-testing". If this is meant to reference "opentelemetry-testing", please correct the spelling. - Reason this comment was not posted:
Comment was on unchanged code.
15. packages/instrumentation-cohere/tests/rerank.test.ts:98
- Draft comment:
Typo in the test data: the string 'beforethe United States' should be 'before the United States' (missing space between 'before' and 'the'). - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
16. packages/instrumentation-langchain/test/instrumentation.test.ts:317
- Draft comment:
Minor typographical suggestion: In the prompt template string on line 317, consider removing the article 'a' so that it reads '...into a search query for Wikipedia:' instead of 'for a wikipedia:'. This will improve the clarity of the text. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
17. packages/instrumentation-pinecone/test/instrumentation.test.ts:34
- Draft comment:
Typo alert: The constant PINECONE_TEST_INDEX is set to "pincone-instrumentation-test". It appears 'pinecone' has been misspelled as 'pincone'. Please confirm if this is intentional, and if not, update it to 'pinecone-instrumentation-test'. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
18. packages/instrumentation-pinecone/test/instrumentation.test.ts:109
- Draft comment:
Minor comment: In the comment on line 109, the text reads "delay before your upserted vectors are available to query ,delete". The comma before 'delete' seems out of place and could be removed or clarified for better readability. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
Workflow ID: wflow_pwfsQRt9NlkR2q20
You can customize
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed 072213e in 1 minute and 21 seconds. Click for details.
- Reviewed
46lines of code in3files - Skipped
0files when reviewing. - Skipped posting
9draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. packages/instrumentation-langchain/test/instrumentation.test.ts:183
- Draft comment:
Minor formatting update to inline llm argument in loadQAStuffChain. No functional change. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
2. packages/instrumentation-pinecone/test/instrumentation.test.ts:137
- Draft comment:
Formatting change for deleteIndex call. Consider awaiting the promise if deleteIndex is asynchronous. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
3. packages/instrumentation-qdrant/tests/instrumentation.test.ts:55
- Draft comment:
Purely a formatting change for setting QDRANT_URL; no functional impact. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
4. packages/instrumentation-langchain/test/instrumentation.test.ts:183
- Draft comment:
Refactored the loadQAStuffChain call for improved formatting. No issues found. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
5. packages/instrumentation-pinecone/test/instrumentation.test.ts:138
- Draft comment:
Consider wrapping single-line if statements with curly braces to improve clarity and prevent bugs in future modifications. - Reason this comment was not posted:
Comment was on unchanged code.
6. packages/instrumentation-qdrant/tests/instrumentation.test.ts:55
- Draft comment:
The reformatting of the QDRANT_URL assignment is stylistic; ensure consistent formatting across the codebase. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
7. packages/instrumentation-langchain/test/instrumentation.test.ts:316
- Draft comment:
Typographical note: In the prompt template string (around line 317), 'into a search query for a wikipedia:' could be improved by capitalizing 'wikipedia' to 'Wikipedia' to match the proper noun usage. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
8. packages/instrumentation-pinecone/test/instrumentation.test.ts:34
- Draft comment:
Typo in the test index name: 'pincone-instrumentation-test' should likely be corrected to 'pinecone-instrumentation-test' to match the proper spelling of 'pinecone'. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
9. packages/instrumentation-pinecone/test/instrumentation.test.ts:109
- Draft comment:
Typo in comment on line 109: The phrase "query ,delete" has an extra comma. Consider revising it to something like "query, delete" or otherwise rephrase for clarity. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
Workflow ID: wflow_3pc0kHf33GOl97Qg
You can customize
nirga
approved these changes
Apr 23, 2025
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.
Important
Update various dependencies and devDependencies to their latest minor and patch versions across multiple packages, and adjust tests accordingly.
@opentelemetry/coreto^1.30.1,@opentelemetry/instrumentationto^0.200.0, and@opentelemetry/semantic-conventionsto^1.32.0in multiplepackage.jsonfiles.@anthropic-ai/sdkto^0.39.0,@azure/openaito^1.0.0-beta.13,@aws-sdk/client-bedrock-runtimeto^3.787.0,@google-cloud/aiplatformto^3.35.0,@google-cloud/vertexaito^1.10.0,@pinecone-database/pineconeto^2.2.2,@qdrant/js-client-restto^1.14.0,cohere-aito^7.17.1,langchainto^0.3.23,llamaindexto^0.10.2,openaito^4.95.1, andtogether-aito^0.15.1in variouspackage.jsonfiles.tslibto^2.8.1in multiplepackage.jsonfiles.@pollyjs/adapter-node-http,@pollyjs/core, and@pollyjs/persister-fsto^6.0.6in multiplepackage.jsonfiles.@types/mochato^10.0.10,ts-mochato^10.1.0,mochato^10.8.2,esbuildto^0.25.3, anduuidto^10.0.0in variouspackage.jsonfiles.instrumentation.test.tsfiles in several packages to initializeBasicTracerProviderwithSimpleSpanProcessor(memoryExporter).This description was created by
for 072213e. You can customize this summary. It will automatically update as commits are pushed.