Skip to content

feat(sei): re-point legis git-rename consumer to /git/rename-feed #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tachyon-beep merged 1 commit into from
Jun 25, 2026
+191 −99
Merged

feat(sei): re-point legis git-rename consumer to /git/rename-feed #73

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,19 @@ only when an incompatible change is made to that surface. See

## [Unreleased]

### Changed

- **SEI git-rename consumer re-pointed to `legis`'s `/git/rename-feed`.**
`LegisGitRenameSource` now reads the committed leg of `legis`'s additive
superset endpoint `GET /git/rename-feed?base=…&head=HEAD` instead of the legacy
`GET /git/renames?rev_range=…`. `legis` pins each `committed[]` entry
byte-identical to the old `/git/renames` array with a contract-lock test, so
committed renames resolve unchanged; the `working_tree` leg is not consumed
(committed-window semantics preserved — the shell source remains the sole
working-tree authority). Enrich-only and fail-soft as before; the wire-drift
guard now warns on a legacy flat-array body or a `committed`-less envelope.
(Federation ledger B3.)

## [1.3.1] — 2026-06-22

Patch release on top of `1.3.0`. (Cargo SemVer `1.3.1`; Python wheels `1.3.1`.)
Expand Down
Loading