[Debugger] Bump minimum Node.js tracer version #28957
Merged
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
While 5.39.0 still technically will work, version 5.48.0 is recommended for the best experience, as it supports all the features available in the UI.
Contributor
Preview links (active after the
|
tylfin
approved these changes
Apr 24, 2025
domalessi
approved these changes
Apr 24, 2025
Contributor
Author
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
dd-devflow
bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
dd-mergequeue
bot
deleted the
watson/debugger-nodejs-bump-traver-version
branch
dd-devflow
bot
added
mergequeue-status: done
and removed
mergequeue-status: in_progress
labels
lkretvix
added a commit
that referenced
this pull request
Apr 25, 2025
…kretvix/dsm-add-new-technology-pages * 'master' of github.com:DataDog/documentation: (33 commits) Update databricks.md (#28979) [SCA] Change Repo Settings Link in SCA Setup + Troubleshooting page (#28975) add recommendation for RabbitMQ integration (#28945) add warning for openai byok (#28813) SDCD-1160: specifying dora change lead time limitation if previous deployment was too far in the past (#28956) Add helm to argocd docs (#28630) added that TCP is not available for gov site (#28972) Translation Pipeline PR (#28965) Update explorer.md (#28970) [DOCS-10642] Add Snowflake section to OP Amazon S3 destination (#28967) remove "preview" callout from datastore docs (#28963) Update check_references.md (#28855) Update Private Location Windows version to 1.56.1 (#28950) Improve Cdocs logging to catch environment issues (#28961) [DOCS-10446] changes to Resource Catalog policies (#28389) Add code snippet for Kotlin Multiplatform (#28954) minor rum edits (#28106) [DOCS-10699] add regions to restricted networks page (#28958) [DJM-218] Remove install logs section in Databricks page (#28948) [Debugger] Bump minimum Node.js tracer version (#28957) ...
estherk15
pushed a commit
that referenced
this pull request
May 8, 2025
While 5.39.0 still technically will work, version 5.48.0 is recommended for the best experience, as it supports all the features available in the UI.
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 does this PR do? What is the motivation?
As the title says. While 5.39.0 still technically will work, version 5.48.0 is recommended for the best experience, as it supports all the features available in the UI.
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes