Skip to content

chore(main): release 4.0.1 - #162

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

rabii-chaarani merged 4 commits into
mainfrom
release-please--branches--main--components--codebase-graph

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

4.0.1 (2026-10-27)

This release replaces the unpublished 4.0.0 proposal (#156). Its production gate failed before any tag or release was created. The storage changes below are included because 3.0.4 remains the last published release.

⚠ 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)

Bug Fixes

  • ci: archive historical Python evidence helpers without changing their bytes, and check repository release policy in ordinary CI (#159) (34eac4f)
  • release: stop replaying old release overrides when a manifest version has no published tag, and stage the four public archive/checksum files for the two supported native targets (#162).

Repair verification

  • Final repair: 260f407. Fresh independent GPT-6.1 Sol / Max review found no confirmed P0–P3 defects; all ten reviewed source/test hashes are unchanged. Review and executed evidence.

  • Fixes COD-100; related production-gate fix COD-99 / fix(ci): archive historical Python helpers and enforce repository gate #159.

  • All workspace packages, dependency constraints, lock entries and the release manifest agree on 4.0.1.

  • Actual release-please 17.6.0 read-only generation confirms the bootstrap cutoff prevents the historical downgrade without a permanent version pin.

  • 44/44 release-tool tests pass (0 skipped), including actual staging Bash that accepts both supported archives/checksums and rejects an incomplete set. Formatting, warnings-denied xtask Clippy, workflow policy, repository gates and version validation pass locally.

  • Durable evidence: docs/testing/release-pr-162/; canonical contract: docs/release.md and original wiki knowledge/architecture/release-verification.md. Scryer ledger chg-9sernm; existing publication/metadata claims are unchanged. User approval: “make it 4.0.1 and resolve the issues first” (2026-10-27).

  • Hosted PR CI and successful exact-source main-merge CI are still required. Nothing has been merged, tagged or published by this repair. Failed chore(main): release 4.0.0 #156 remains unpublished and is not falsely marked tagged.

  • Until this repair merges, an ordinary main CI completion can overwrite it because the bot still reads the old main config. No workflow settings or release labels were changed to bypass that limitation.


This PR was generated with Release Please, then repaired for the approved 4.0.1 recovery. Existing exact-SHA CI, production, native artifact and crates.io gates remain intact.

Resolve COD-100 / GH-162 under existing release contracts. Supersede unpublished 4.0.0 without fabricating a tag; bound release-please fallback history and stage the two-target asset set. Preserve exact-SHA publication gates and retain executed evidence and independent review.
@rabii-chaarani rabii-chaarani changed the title chore(main): release 1.2.2 chore(main): release 4.0.1 Oct 27, 2026
@rabii-chaarani
rabii-chaarani merged commit 9557b38 into main Oct 27, 2026
21 checks passed
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