docs(agents): record 0.22.0 release, #892/#894 landings, 2026-08-28 tracker items - #904
Merged
Conversation
…racker items - Update the three release-state claims: PR #793 (two-phase save) and PR #843 (lock-free pickle-family backends) shipped in 0.22.0 on 2026-08-28; note fix(query) #894 is in the tag despite being absent from the generated changelog. - Move PR #894 (latest/oldest raise ValueError when no matching call carries Runtime metadata), PR #892 (gc mid-sweep guards + digest product collapse, suite 1738 -> 1299), and docs-audit PRs #873/#874 from in-flight to landed; the in-flight section now just points at the five open PRs covered under their themes. - Record the 2026-08-28 refactor cohort #899-#902 and bug #903 (put() filelock.Timeout fatality on <=0.21.2, resolved for pickle-family by 0.22.0's atomic rename); note the #895 resolution as a documented limitation. - USAGE.md: state the latest()/oldest() ValueError/IndexError contract. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014myhh6xKWC2VhQeB92mGSn
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
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.
Scheduled AGENTS.md audit. Changes since the 2026-08-27 pass:
fix(query)fix(query): raise instead of silently picking an arbitrary latest()/oldest() #894 is an ancestor of the 0.22.0 tag (verified viagit tag --contains c82c691) even though the generated changelog entry omits it.latest()/oldest()raiseValueErrorwhen no matching call carriesRuntimemetadata,IndexErroron empty), PR test: cover Cache.gc()'s mid-sweep races; collapse the 21x21 digest product #892 (gc mid-sweep guards + 441-case digest product collapse, suite 1738 → 1299), and docs-audit PRs docs(usage): fix inaccurate/misleading claims in tldr, helpers, query #873/docs(installation,parallel_execution): fix quoting bug, trim duplication, close gaps #874 moved from the in-flight section to decisions landed; the in-flight section is now a one-liner pointing at the five PRs still open (fix(state): serialise BoundWrapper.func by value when not importable by reference #887, fix(benchmarks): don't measure hit-phase timing against evicted keys #804, feat(storage): cache filesystem paths by content #797, fix(storage): cache open HDF5 read handles for multi-bag bag files #786, remove isolate from fleche decorator #523), each covered under its theme.put()filelock.Timeoutfatality on ≤0.21.2, dedup-concentrated lock contention; resolved for pickle-family by 0.22.0's atomic rename, bagofholding multi-bag still exposed per bagofholding_file prefix-bag writes: filelock.Timeout storms at the 1.0 s default under same-bag concurrency (measured; not a deadlock) #893), and the wrap_executor: cache-hit Future is always stdlib Future, even for executors that return a different Future subtype #895 resolution (documented limitation per the 2026-08-28 maintainer comment). Refactor: pypi-publish.yml and release-please.yml duplicate the whole build+publish sequence — and can both fire on the same release #900 cross-referenced at thepypi-publish.ymlline in the workflows list.lock_timeoutmitigation sentence rephrased to the current state: theFutureWarningdrop covers only pickle-family configs, a bagofholdingvalues.lock_timeoutstill works on 0.22.0 (checked againstconfig.py:466).latest()/oldest()ValueError/IndexErrorcontract (verified againstquery.py:149-188).landau's AGENTS.md was audited in the same pass and left unchanged — no code or tracker movement since its 2026-08-24 update (only docs commits on main; issues #423–#425 and PRs #422/#414/#395/#394/#391 unchanged).
🤖 Generated with Claude Code
https://claude.ai/code/session_014myhh6xKWC2VhQeB92mGSn
Generated by Claude Code