update upgrade notes for new major version #32905
Merged
+283
−102
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
Contributor
Preview links (active after the
|
brettlangdon
approved these changes
Nov 18, 2025
content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/python.md
Outdated
Show resolved
Hide resolved
content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/python.md
Outdated
Show resolved
Hide resolved
content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/python.md
Outdated
Show resolved
Hide resolved
…dd_libraries/python.md Co-authored-by: Brett Langdon <[email protected]>
Contributor
duncanhewett
left a comment
duncanhewett
left a comment
There was a problem hiding this comment.
A couple of general points:
- We should keep the v3 upgrade guide rather than replace it because it's still relevant for customers on <v3. I think it would be best to have a separate page for each upgrade and link from the main page, similar to this Go page.
- Some tidy up is needed with the formatting and to address the vale warnings.
Contributor
Author
|
@duncanhewett I re-included the v3 notes. Do you think it's ok to create the subpage in a separate change? |
brett0000FF
approved these changes
Nov 19, 2025
Contributor
brett0000FF
left a comment
brett0000FF
left a comment
There was a problem hiding this comment.
@emmettbutler - Awesome, thank you! I went ahead and moved the content into separate files. While moving the content, I made a few edits to your content so it fits better on a standalone page. Please let me know if you have any questions. Thanks again! 🚀
duncanhewett
approved these changes
Nov 19, 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.
What does this PR do? What is the motivation?
Public upgrade instructions for the new major version of ddtracepy, currently in the release-candidate stage: https://github.com/DataDog/dd-trace-py/releases/tag/v4.0.0rc2
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass 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.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes