Repository navigation
chore: release 0.55.0 - #325
Merged
sunerpy merged 2 commits intoOct 21, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #325 +/- ##
==========================================
- Coverage 95.60% 95.60% -0.01%
==========================================
Files 280 280
Lines 166327 166327
==========================================
- Hits 159013 159012 -1
- Misses 7314 7315 +1 see 2 files with indirect coverage changes 🚀 New features to boost your workflow:
|
sunerpy
deleted the
release-please--branches--main--components--codegraph-rs
branch
October 21, 2026 14:05
Contributor
Author
|
🤖 Created releases: 🌻 |
sunerpy
added a commit
that referenced
this pull request
Oct 22, 2026
…329) 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.
sunerpy
added a commit
that referenced
this pull request
Oct 22, 2026
…ng it (#330) * fix(daemon): upgrade an outdated index before the daemon starts serving it In the default daemon mode nothing upgraded an index an older extraction version built. A cold `serve --mcp` session defers to its daemon, and the daemon's startup gate admits only a current index, so every tool call answered "outdated" until a manual `codegraph sync`. v0.55.0 moved the extraction version from 21 to 22, so every v0.54.0 index hit this. The daemon now upgrades the index before its startup gate, through a new codegraph-watch entry, upgrade_outdated_index_once. Under one exclusive lease it requires an outdated namespace whose authoritative slot records the current phase, no uninitialized tombstone, and the database file, and only then runs the migration `codegraph sync` runs. The state gate classifies every phase an older version wrote as outdated, so without these checks a daemon would rebuild the database an older `uninit --force` removed. Anything else, and a failed upgrade, is left to the unchanged gate, which refuses it as before. * fix(test): give every plain_output project its own temporary directory Two tests that started within one clock tick shared a directory, and the first to finish deleted the other's project mid-run, as in the first CI attempt of #325. The name now carries a process-wide sequence, and the directory is created with create_dir, so a collision fails instead of sharing. * docs(cli): say what a daemon leaves when its upgrade fails partway The upgrade runs the migration `codegraph sync` runs, which publishes `phase=building` before it removes the old database, so a rebuild that fails partway leaves the index `building`, as an interrupted `sync` does, and the daemon refuses it. The upgrade section said only that a later tool call succeeds. * fix(daemon): stop a daemon whose upgrade fails before its startup gate A failed upgrade is a failed migration, and a migration failure must stop. The daemon logged the error and went on to its startup gate. The last step of the rebuild publishes `Current`, and the publisher's directory sync can still fail after that, so the gate could serve an index whose upgrade had just reported an error. The daemon now refuses to start with that error, before the gate, and publishes no pid or socket. A later daemon finds the index as the failure left it, and the gate decides as before. docs/cli.md now says what a failed rebuild can leave: the older index untouched if it fails before it begins replacing it, `building` if it fails later, as an interrupted `sync` does.
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.
🤖 I have created a release beep boop
0.55.0 (2026-10-21)
Features
Bug Fixes
Performance Improvements
This PR was generated with Release Please. See documentation.