Repository navigation
Conversation
![veria-ai[bot]](https://avatars.githubusercontent.com/in/1723776?s=60&v=4){kind=small}
PR overviewAll previously flagged issues have been addressed. No open security concerns remain on this pull request. Security reviewNo open security issues remain on this pull request. Fixed/addressed: 1 · PR risk: 0/10 |
eli-r-ph
force-pushed
the
v1-capture-redirects
branch
from
October 10, 2026 00:32
bcd36eb to
be748d9
Compare
eli-r-ph
force-pushed
the
v1-sync-main
branch
from
October 10, 2026 00:32
080dd29 to
94db31b
Compare
* ci: reuse Python SDK upgrade PRs unless queued * ci: protect reused upgrade PRs from stale and queued writes (cherry picked from commit 945bbbc)
* feat(error-tracking): standardize exception metadata * fix(error-tracking): preserve explicit trace context * fix(error-tracking): restrict exception group traversal * fix(error-tracking): deprecate reserved property overrides * fix(error-tracking): bound exception group traversal (cherry picked from commit 6d6cc3d)
(cherry picked from commit c4e6bdd)
(cherry picked from commit 50efa65)
* feat(asgi): add error tracking middleware * chore(asgi): type exception capture metadata * fix(asgi): make tracing header trust explicit * refactor(asgi): expose request properties terminology (cherry picked from commit 1c6a47a)
* feat(mcp): resolve fresh low-level tool ownership Add resolve_original_tool for raw MCP SDK 1.x and 2.x servers. Prefer ownership learned from a served listing and keep unknown ownership fail-open. Generated-By: PostHog Desktop Task-Id: db1a8a08-fe03-43b6-9e49-705e8b1f375e * fix(mcp): preserve listed argument ownership Generated-By: PostHog Desktop Task-Id: db1a8a08-fe03-43b6-9e49-705e8b1f375e * fix(mcp): preserve arguments for unknown schemas Generated-By: PostHog Desktop Task-Id: db1a8a08-fe03-43b6-9e49-705e8b1f375e * fix(mcp): preserve low-level tool schemas Generated-By: PostHog Desktop Task-Id: db1a8a08-fe03-43b6-9e49-705e8b1f375e (cherry picked from commit 127009d)
* feat(flask): add error tracking integration * fix(flask): use canonical exception metadata * chore(flask): type exception capture metadata * refactor(flask): expose request properties terminology * fix(flask): preserve exception privacy settings (cherry picked from commit 292855d)
(cherry picked from commit d23ef68)
(cherry picked from commit c0e05b1)
* feat(drf): add automatic error tracking integration * fix(drf): align exception metadata with SDK spec * chore(drf): type exception capture metadata * fix(drf): honor Django request filtering * test(drf): describe context data as properties * feat(drf): support exception capture opt-out * chore(drf): update public API snapshot * fix(drf): align exception capture configuration * test(drf): preserve omitted setting default (cherry picked from commit 9baf8a5)
(cherry picked from commit a655c8b)
(cherry picked from commit 509c852)
eli-r-ph
force-pushed
the
v1-capture-redirects
branch
from
October 10, 2026 03:19
be748d9 to
ea73def
Compare
eli-r-ph
force-pushed
the
v1-sync-main
branch
from
October 10, 2026 03:19
94db31b to
5f2f116
Compare
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
💡 Motivation and Context
Stacked on #1035. Part of the 8.0 series (checklist in #1016). Note: I was trying to avoid an explicit merge/rebase onto
v1without a PR, but this PR is huge! I can do this another way (or split) if preferable, these changes should merge smoothlyBrings everything that landed on
mainsincev1forked into the 8.0 series, so 8.0 doesn't drop it:Each upstream commit is cherry-picked with
-x, inmainorder, so you can review it against its original PR. About 10.7k of the ~14.5k changed lines are the generatedreferences/*.jsonfrom the release commits, so reviewing by commit and skipping those files leaves ~3.8k lines.Only #898 needed hand resolution:
capture_exceptiondocstring: keepsv1's "and options" and adds feat(error-tracking): standardize exception event metadata #898's deprecation sentence verbatim. Whether 8.0 enforces that deprecation is a separate PR.test_excepthook: keepsv1's v1-response assertions and adds feat(error-tracking): standardize exception event metadata #898's new ones. It dropsmain's v0 "data uploaded successfully" log check.v1's exception-list prefix check hardcoded the pre-feat(error-tracking): standardize exception event metadata #898 mechanism, so it becomes atype/valuecheck.💚 How did you test it?
git merge-treeof fix!: follow capture redirects only to the configured origin #1035's tip withmain, apart from the two hand-resolved files above.test_excepthook.ruff,mypy(baseline filter),make public_api_check,python -W error -c "import posthog",uv lock --checkand the fullpytestsuite (including the new Flask, ASGI and DRF tests on the v1 send path) pass locally.📝 Checklist
If releasing new changes
sampo addto generate a changeset file🤖 Agent context
Autonomy: Human-driven (agent-assisted)
v1. Cherry-picks keep the stack linear for restacks. Squash merges don't record merge history, somainstill shows as unmerged. A no-content merge to record that history is planned for after the series lands.