Skip to content

chore: release 0.55.1 - #331

Merged
sunerpy merged 1 commit into
mainfrom
release-please--branches--main--components--codegraph-rs
Oct 22, 2026
Merged

sunerpy merged 1 commit into
mainfrom
release-please--branches--main--components--codegraph-rs

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.55.1 (2026-10-22)

Bug Fixes

  • daemon: upgrade an outdated index before the daemon starts serving it (#330) (b6f0106)

This PR was generated with Release Please. See documentation.

@codecov

codecov Bot commented Oct 22, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #331      +/-   ##
==========================================
- Coverage   95.59%   95.59%   -0.01%     
==========================================
  Files         280      280              
  Lines      166400   166400              
==========================================
- Hits       159076   159075       -1     
- Misses       7324     7325       +1     

see 3 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@sunerpy
sunerpy merged commit 44fd8af into main Oct 22, 2026
11 checks passed
@sunerpy
sunerpy deleted the release-please--branches--main--components--codegraph-rs branch October 22, 2026 09:19
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

sunerpy added a commit that referenced this pull request Oct 22, 2026
Release-please PR #331 merged as 44fd8af and tag v0.55.1 was cut there. Release run 39754559422 passed all twelve jobs, and the downloaded release passed the black-box acceptance: an index built by v0.54.0 or v0.53.0 is upgraded by a cold session's daemon, and by a replacement daemon, with no manual sync. A second entry records #330's fix and the pre-existing sync behavior it leaves alone.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant