Skip to content

chore(main): release 4.0.0 - #156

Merged
rabii-chaarani merged 1 commit into
mainfrom
release-please--branches--main--components--codebase-graph
Oct 27, 2026
Merged

rabii-chaarani merged 1 commit into
mainfrom
release-please--branches--main--components--codebase-graph

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

4.0.0 (2026-10-27)

⚠ BREAKING CHANGES

  • storage: database open helpers return GuardedDatabase and reject path forms whose native resource identity cannot be proven. Connections borrow the guarded handle; canonical Windows extended paths retain their namespace.

Features

  • storage: automate graph disk cleanup and controlled legacy retirement (#153) (75a99c8)

This PR was generated with Release Please. See documentation.

@rabii-chaarani

Copy link
Copy Markdown
Owner

4.0.0 recovery / COD-100: this proposal remains unpublished. Its exact merge 7038e66ff8271ffddc511f879cf8d28353a09b2d passed its own CI but failed the production repository gate in run 40453997235, before a tag/release/crate was created. PR #159 fixes the evidence layout only on newer main; it cannot make this immutable source pass.

The maintainer requested 4.0.1 on 2026-10-27. Corrected replacement proposal #162 retains the unpublished storage feature and breaking-change notes, fixes generator history replay and the two-target asset-staging count, and must pass its own PR and exact-main-merge release gates. This supersedes the failed proposal, not a published release. No v4.0.0 tag is fabricated and this PR is not marked tagged. Tracking: COD-100.

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