Repository navigation
chore: cut 0.0.115 - #710
Merged
Merged
Conversation
The file link a channel turn writes gets a SAVEPOINT of its own — #703, refs #690. #634 landed the linking itself. What was left, and what this releases, is the transaction it rides: the link was written inside the SAVEPOINT the whole transcript shares, so an exception from it rolled back the user turn, the settled calls and the assistant message with its tool calls — for a run that had already spent money, over a file. It also adds the test #690 actually asked for: one that reads the column back off a real database rather than asserting at the repository boundary. `link_to_message` was never the broken part; that no surface but web chat called it was. Version bumped in `backend/pyproject.toml`, `backend/uv.lock` and `frontend/package.json`. The CHANGELOG entry is written here rather than promoted from `[Unreleased]`, because #703 wrote none.
DEENUU1
added a commit
that referenced
this pull request
Aug 15, 2026
The file link a channel turn writes gets a SAVEPOINT of its own — #703, refs #690. #634 landed the linking itself. What was left, and what this releases, is the transaction it rides: the link was written inside the SAVEPOINT the whole transcript shares, so an exception from it rolled back the user turn, the settled calls and the assistant message with its tool calls — for a run that had already spent money, over a file. It also adds the test #690 actually asked for: one that reads the column back off a real database rather than asserting at the repository boundary. `link_to_message` was never the broken part; that no surface but web chat called it was. Version bumped in `backend/pyproject.toml`, `backend/uv.lock` and `frontend/package.json`. The CHANGELOG entry is written here rather than promoted from `[Unreleased]`, because #703 wrote none.
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
1 participant
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.
The file link a channel turn writes gets a SAVEPOINT of its own — #703, refs #690.
#634 landed the linking itself. What was left, and what this releases, is the
transaction it rides: the link was written inside the SAVEPOINT the whole
transcript shares, so an exception from it rolled back the user turn, the settled
calls and the assistant message with its tool calls — for a run that had already
spent money, over a file.
It also adds the test #690 actually asked for: one that reads the column back off
a real database rather than asserting at the repository boundary.
link_to_messagewas never the broken part; that no surface but web chat calledit was.
Version bumped in
backend/pyproject.toml,backend/uv.lockandfrontend/package.json. The CHANGELOG entry is written here rather than promotedfrom
[Unreleased], because #703 wrote none.