Repository navigation
Conversation
…es it can create Signed-off-by: Bogdan Szabo <bogdan@re-cinq.com>
This was referenced Nov 2, 2026
gedaiu
added a commit
to re-cinq/lore
that referenced
this pull request
Nov 2, 2026
Bumps the Utopia pin to `0.1.0-re.28` (digest `sha256:4ddd146f…`), the re-dev head after one fork merge: - re-cinq/utopia#47: a write token may rename, delete, re-extract and clean up the missing documents of a `statements` or `api` source. Those routes took only a session, so Lore's personal token got a 401 on them: the history source split, the history extraction switch and the missing-item sweep (#4079) never ran. Other source kinds stay session-only (`token_source_kind`). Upstream: deeplethe/utopia#1474. No new migration. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi! A write token can already create a statements or api source, but keeping it tidy afterwards (renaming it, deleting it, re-extracting it, cleaning up missing documents) still needed a session. A service mirroring a repo had no way to do those without holding someone's seven day login.
This lets those four routes take a write token too, for push sources only, with the same guards as creating one. Url, rss and custom sources stay session only and answer
token_source_kind, so a leaked token still can't point the server at a new address. The audit rows carry the token id, and ADR 0014 has a dated note.Two tests cover it, one per side, and both fail without the change.
Thank you for taking a look!