Repository navigation
docs(upstream): record the v0.55.0 release and close the v1.6.2 sync - #329
Merged
Merged
Conversation
Record the v0.55.0 release: #322 merged as 0796c8a, release PR #325 as 5f96a74, the push event GitHub never delivered for that merge, #327's dispatch path, Release run 39698634632, and the black-box acceptance of the downloaded binaries against v0.54.0, with the 24-cell benchmark and the older upgrade issue in default daemon mode. Close the v1.6.1 -> v1.6.2 sync: the tracked release moves to v1.6.2 with the owner's exceptions (COBOL, G16 and G17, OD-19, and the W7-W9 rows planned for the follow-up pull request). The audit's LANDED rows now name #322, and docs-check.py expects the new tracked release.
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #329 +/- ##
==========================================
- Coverage 95.60% 95.60% -0.01%
==========================================
Files 280 280
Lines 166327 166327
==========================================
- Hits 159018 159013 -5
- Misses 7309 7314 +5 see 4 files 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.
Summary
Records the v0.55.0 release in
docs/upstream-sync/UPSTREAM.mdand closes the colbyv1.6.1 → v1.6.2sync.0796c8a, release PR chore: release 0.55.0 #325 →5f96a74.5f96a74, and ci(release): accept the release PR's CI when its push event is lost #327's guarded dispatch path.39698634632that passed all twelve jobs.outdatedindex is never upgraded on its own; onecodegraph syncis needed. v0.54.0 behaves the same on a v0.53.0 index. The owner chose a patch release for the fix.v1.6.2, with the owner's exceptions: COBOL, G16/G17, OD-19, and the W7–W9 rows planned for the follow-up pull request. The next discovery boundary is unchanged.LANDEDrows now name feat: port the colby v1.6.2 extraction, resolution and sync semantics #322; oxfmt realigned their tables.scripts/docs-check.pyexpects the new tracked release.UPSTREAM.mdis in.oxfmtignore, so its older entries are byte-identical; only the alignment bullets above change and the two new entries are added.Testing
python3 scripts/docs-check.pyandoxfmt --checkpass.make pre-cipassed:make check, the viewer gate (vitest 574/574) and the archive smoke.