Repository navigation
chore(deps): declare the bridge's exclude-newer window explicitly - #48
Merged
Merged
Conversation
The bridge had no window of its own. uv applied the root pyproject.toml's as parent-directory configuration, so the behaviour was right but the reason was invisible: nothing in packages/tablecodec-docling said seven days, and extracting the package to its own repository (ADR 0013) would have dropped the window without anyone noticing. Declaring `[tool.uv] exclude-newer = "7 days"` states what was already happening. `uv.lock` is byte-unchanged and `uv lock --check` passes inside the bridge directory with no environment variable set, which is the proof the explicit value matches the inherited one exactly -- the lock already recorded `exclude-newer-span = "P7D"`. `[tool.uv]` goes above `[tool.uv.sources]` and `[[tool.uv.index]]` so the super-table is defined before its children rather than after. `just docling-ci` passes, 30 tests. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LXPmm8VuMHBjo4Q6k7tRtq
docs/handover.md loses the Known Risk about the bridge inheriting the core's exclude-newer -- the bridge declares its own now, so there is nothing left to lose on extraction. 576 words. docs/release.md says so in the cutoff subsection, one sentence. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LXPmm8VuMHBjo4Q6k7tRtq
hironow
added a commit
that referenced
this pull request
Sep 4, 2026
One `docs:` commit, one file, nothing else touched. ## Why `Last updated` still read 15:04 (JST) although #37, #38, #44, #45, #46, #47 and #48 have all changed the document's body since. A stale stamp on a handover is worse than none: it tells the next reader the content is older than it is. ## What changed The stamp, and the tail of the Current State paragraph. It claimed the only movement since the release was "tooling and Dependabot bumps", which stopped being the whole story hours ago. It now names today's arrivals in three sentences: - `exclude-newer` became a relative seven-day window (ADR 0015), which unblocked the Dependabot `uv` updater after six weeks of failures. - The screened index is declared in both `pyproject.toml`s, the workflows and `dependabot.yaml`, so every lockfile records it — the bridge's included. - The `protect` ruleset requires eleven status checks, and CI calls the justfile recipes rather than its own copies, so the justfile alone defines what lint and type checking cover. ## Verification - 649 words, inside the 650 budget. - `mise exec -- markdownlint-cli2` reports 0 errors. - `just ci` passes. - The diff touches `docs/handover.md` only. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01LXPmm8VuMHBjo4Q6k7tRtq Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
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
1 participant
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.
Two commits. Closes the last implicit piece of the screened-resolution setup.
Why
packages/tablecodec-doclinghad noexclude-newerof its own. uv applied theroot
pyproject.toml's as parent-directory configuration, so the behaviour wasalready right — but the reason was invisible. Nothing in the bridge said seven
days, and extracting it to its own repository (ADR 0013) would have dropped the
window with nobody noticing.
The proof it changes nothing today
uv.lockis byte-unchanged, anduv lock --checkpasses inside the bridgedirectory with no environment variable set. That is the evidence the explicit
value matches the inherited one exactly: the lock already recorded
exclude-newer-span = "P7D", and it still does.uv lock --check(bridge dir, no env var, uv 0.11.17)packages/tablecodec-docling/uv.lockjust docling-cijust citool.uvresolves toexclude-newer,sources,indextogether[tool.uv]is placed above[tool.uv.sources]and[[tool.uv.index]]so thesuper-table is defined before its children rather than after it — unambiguous
regardless of how strict the parser is.
Docs
docs/handover.mddrops the Known Risk about the inherited window; there isnothing left to lose on extraction. 576 words.
docs/release.mdrecords it inthe cutoff subsection, one sentence. ADR 0015 untouched — this states its
decision in one more place, it does not change it.
🤖 Generated with Claude Code
https://claude.ai/code/session_01LXPmm8VuMHBjo4Q6k7tRtq