Repository navigation
docs(upstream-sync): record the post-1.5.0 triage and four shipped tiers - #219
Merged
Merged
Conversation
Upstream's newest tag is still v1.5.0, so a version-delta sync had nothing to pull — but `main` had accumulated 104 unreleased commits past that tag, and two months of issues had never been triaged. The ledger now says so, and the header tells the next sync to diff `v1.5.0..origin/main` rather than trusting the tag list alone. Records the five releases this round produced, the two agent findings that dissolved on measurement (candidate ordering and the staleness banner were both already correct), the upstream premise upstream itself measured and rejected, and the telemetry / vector-RAG divergences that our guardrail makes permanent. Tracked parity stays 1.5.0: none of these releases ports an upstream release range.
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #219 +/- ##
=======================================
Coverage 95.28% 95.28%
=======================================
Files 140 140
Lines 77287 77287
=======================================
+ Hits 73643 73644 +1
+ Misses 3644 3643 -1 see 1 file with indirect coverage changes 🚀 New features to boost your workflow:
|
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.
Ledger entry for the round that shipped
v0.43.2→v0.45.0.Why this round existed at all
git ls-remote --tagsstill reports v1.5.0 as upstream's newest tag, so a version-delta sync had nothing to pull. Butmainhad accumulated 104 unreleased commits past that tag (43 source files, +5737/−368), and issues #1496–#1566 / PRs #1402–#1564 had never been triaged."No new version" is not "no new content". The header now instructs the next sync to diff
v1.5.0..origin/maintoo, so this is not rediscovered from scratch.What the entry records
v0.43.2v0.43.3v0.44.0interfaceas containersv0.44.1v0.45.0invokecall sitesPlus the dispositions that matter more than the ports:
explorestaleness banner were both already correct — the first because both production resolution contexts sort themselves with a stricter key than upstream's, the second because the banner is prepended after truncation and a cut section's citation is dropped first. Recorded so the next sync does not re-investigate.scripts/guardrail.shmakes structural rather than a matter of preference.Verification
Every number in the entry was re-derived before committing: 104 commits and
43 files changed, 5737 insertions(+), 368 deletions(-)from the upstream clone, upstream's tag stillv1.5.0, and each cited code location re-checked — two line references were corrected in the process (context.rs:111,125andsnapshot_context.rs:118-124, not the numbers I first wrote).Docs only: one file,
oxfmtidempotent. Tracked parity stays1.5.0— none of these releases ports an upstream release range.