v2.1.54

Commits

• 8dd893b release: 2.1.54 notes describe only what changed since 2.1.53 (Codex review of 8cfd54d: MED)
• 9b422e0 release: 2.1.54
• fd4b0ce docs(T-10284): one CHANGELOG entry, not one heading per draft (rebase onto c591515)
• db73641 fix(T-10284): the release waits under asyncio.timeout, so on Python 3.11 a cancellation that lands after the reply is not lost; the cap's docstring claims only what it orders (Opus xhigh review of 38dee82: LOW x2)
• 58bc151 fix(T-10284): a read cancelled during its own release leaves its group for the next read (Codex review of 3b9e890: LOW)
• aed04bb fix(T-10284): leftovers carry the order they were first left in, so overlapping releasers cancelled in any order still drop the oldest (Codex review of 941766f: LOW)
• 7e2e8a9 fix(T-10284): groups put back by a cancelled leftover release go ahead of newer ones, so the cap still drops the oldest (Codex review of 03f018c: LOW)
• 79506b7 fix(T-10284): a read cancelled while releasing earlier leftovers puts back the groups not yet released; the CHANGELOG drops a failure breakdown that was not re-measured (Codex review of 8c19f72: LOW x2)
• 4aca986 fix(T-10284): a failed or cancelled read leaves its object group on the tab for the next read instead of handing the release to a task that can outlive the loop (review of f7734fa: LOW)
• 9c1c2d1 fix(T-10284): the frame search classifies per frame, the object-group release never holds the caller, and a listing reads each row's connectivity once (review of 3f9cc1d: HIGH, MED, LOW)
• 4fa3deb fix(T-10284): the click and listing reads run in an isolated world; a failed read is never an answer; reads release what they resolve (Codex round 8 findings 1-5; closes T-10299)
• 5251df1 fix(T-10284): native reads take the farthest owner on the node's chain; a failed visibility read raises; the read-only scripts send no user gesture; census and docs (review round 2 findings 1-6)
• 13a2fe2 fix(T-10284): native reads walk the node's own prototype chain, so a page's own global Node breaks nothing; the synthetic click has its own answer for an unread connectivity; wait_for_element uses VISIBLE_JS (review findings 1-5)
• c9f9f29 fix(T-10284): one token-returning connectivity read; a failed read is a ToolError, never a departure or a connected node (Codex findings 1-4)
• 0f6a0f2 fix(T-10284): refresh_element also reads isConnected, so a node the page removed but still references is dropped from query_elements and refused by get_element_state
• c591515 fix(T-10522): one retry budget per call; a refusal claims a holder check only when one ran (Codex round 3 MED, MED)
• f05a0e1 fix(T-10522): never sleep while the target is displaced; report only what was observed (Codex round 2 HIGH, MED)
• 7d1c623 fix(T-10522): a copy refused for a lock something else holds no longer reports target-in-use
• 4756bc4 ci(T-10499): pin DevinoSolutions/artifact v1.2.2 (67676f3): a Cloudflare 520-524 from the store is retried, not a failed release
• df25153 test(T-10034): the fingerprint's compile of the package's own source is declared as never executed, so the host-exec inventory stays exact (lane: test_security_boundary)
• 5b88ceb fix(T-10034): a declared fingerprint must be an exact tuple of exact strings, so a caller's str subclass that equals every word ships nothing (Codex review of 200ab62: HIGH)
• f4f62a1 fix(T-10034): the class map covers whole modules of the libraries the package handles, a thread that cannot start cannot stop sentry_init, and an empty map is said once (review of e03fd55: MED, LOW, LOW)
• 7bfee36 fix(T-10034): third-party exceptions our code handles keep their names, and the code map is warmed off the event path
• 6f6121e fix(T-10034): identity, not self-description, decides what a fingerprint may name (Codex round 4: HIGH x3, MED)
• c102474 fix(T-10034): the ToolError fingerprint reads no name a caller's code can set: types, frames and tool names are allowlisted by where they live
• 0534119 fix(T-10034): a ToolError is fingerprinted by tool, error types and our innermost frame, never by its message
• ff8d00c fix(T-10034): the ToolError fingerprint is redacted before it is templated, keeps quoted causes, and names the tool
• 1585362 fix(T-10034): a freeze or a tool error is one Sentry issue, not one per message: a stable fingerprint names the kind and its stable cause