Skip to content

docs(upstream): record the v0.52.1 release - #294

Merged
sunerpy merged 1 commit into
mainfrom
docs/upstream-v0.52.1-release
Oct 1, 2026
Merged

sunerpy merged 1 commit into
mainfrom
docs/upstream-v0.52.1-release

Conversation

@sunerpy

@sunerpy sunerpy commented Oct 1, 2026

Copy link
Copy Markdown
Owner

Summary

This records the v0.52.1 release in docs/upstream-sync/UPSTREAM.md, as #290 did for v0.52.0. The Current alignment block gains a "Shipped in v0.52.1" bullet for #291 and #292. A new dated release entry covers:

  • release workflow run 36879201833, which passed all twelve jobs on its second attempt after a transient Actions-cache 503 broke Windows Clippy on the release commit;
  • the published digest;
  • the black-box acceptance against the official v0.52.0.

The diff only adds lines; no earlier entry changes.

Verification

make tools-check fmt-check docs-check passes. UPSTREAM.md is in .oxfmtignore. The acceptance results quoted come from /tmp/verify-0.52.1.sh run against the downloaded release:

🤖 Generated with Claude Code

The release record for #291 and #292: the workflow run and its re-run past a transient cache outage, the published digest, and the black-box acceptance against v0.52.0.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d660c5da51

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +139 to +143
### 2026-10-01 — `v0.52.1` RELEASED: #291 and #292 shipped

Release-please PR [#293](https://github.com/sunerpy/codegraph-rust/pull/293)
merged as `9ca7f9716de38828562295cdc79a3b5a99b52738` and cut tag `v0.52.1` at
that exact commit.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Record the implementation-to-release provenance

When this append-only ledger is later used to audit v0.52.1, the entry begins with release PR #293 and never records the immutable PR-head and merge SHAs for implementation PRs #291 and #292. Consequently, it does not preserve the required implementation-head → merge → tag chain even though it claims those changes shipped; add the exact implementation provenance before the tag/workflow evidence.

AGENTS.md reference: AGENTS.md:L186-L187

Useful? React with 👍 / 👎.

@codecov

codecov Bot commented Oct 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #294      +/-   ##
==========================================
- Coverage   95.31%   95.31%   -0.01%     
==========================================
  Files         161      161              
  Lines       99130    99130              
==========================================
- Hits        94487    94484       -3     
- Misses       4643     4646       +3     

see 2 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 cd95c65 into main Oct 1, 2026
10 checks passed
@sunerpy
sunerpy deleted the docs/upstream-v0.52.1-release branch October 1, 2026 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant