-
Notifications
You must be signed in to change notification settings - Fork 1.9k
chore: updated open telemtry package versions #5672
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
Conversation
Thank you for following the naming conventions for pull request titles! 🙏 |
WalkthroughThe changes update several OpenTelemetry package dependencies in the Assessment against linked issues
Possibly related PRs
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 2
🧹 Nitpick comments (1)
apps/web/package.json (1)
44-50
: Consider adding a lock file updateWhen updating multiple related packages with significant version changes, it's important to ensure the lock file is updated as well to capture the resolved dependency tree.
Make sure to commit the updated package-lock.json or yarn.lock file along with these changes to ensure consistent dependency resolution across environments.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yaml
is excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (2)
apps/web/instrumentation-node.ts
(2 hunks)apps/web/package.json
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (6)
- GitHub Check: Build Formbricks-web / Build Formbricks-web
- GitHub Check: Run E2E Tests / Run E2E Tests
- GitHub Check: Run Unit Tests / Unit Tests
- GitHub Check: SonarQube
- GitHub Check: Validate Docker Build
- GitHub Check: Analyze (javascript)
🔇 Additional comments (1)
apps/web/package.json (1)
44-50
:✅ Verification successful
Verify removal of @opentelemetry/api-logs
The AI summary indicates that
@opentelemetry/api-logs
was removed from dependencies. Ensure that this package's functionality is now covered by other packages (possibly by the updated@opentelemetry/sdk-logs
).
🏁 Script executed:
#!/bin/bash # Check for any usage of api-logs in the codebase echo "Searching for imports of @opentelemetry/api-logs:" rg -l "@opentelemetry/api-logs" --type tsLength of output: 150
To be thorough, let’s search all file types for any lingering references:
🏁 Script executed:
#!/bin/bash # Search for any references to @opentelemetry/api-logs in the entire codebase echo "Searching for references to @opentelemetry/api-logs in codebase:" rg -n "@opentelemetry/api-logs"Length of output: 818
Removal of @opentelemetry/api-logs Verified
No imports or code references to
@opentelemetry/api-logs
were found outside of lockfile entries, so removing it fromapps/web/package.json
is safe. Its functionality is now provided by the upgraded@opentelemetry/sdk-logs
.
|
What does this PR do?
Fixes #5378
How should this be tested?
test open telemetry setup
Checklist
Required
pnpm build
console.logs
git pull origin main
Appreciated
Summary by CodeRabbit
@opentelemetry/api-logs
package from dependencies.