chore: adopt typed Steda executor errors and bump to 0.1.3 - #88
Merged
Merged
Conversation
zerosnacks
enabled auto-merge (squash)
September 22, 2026 23:13
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.
Summary
This PR updates Kival to Steda 0.1.3 and adopts its typed executor error support for notification projection.
Previously, the projection worker used Steda’s error type directly at the task boundary. With Steda 0.1.3, reusable
TaskExecutorimplementations can expose their own associated error type and let Steda perform the conversion once at the worker boundary.The notification projection executor now uses:
which keeps the implementation focused on its actual domain and allows ordinary
?propagation for database operations.The workspace dependency and lockfile are also updated to Steda 0.1.3.
There was no useful attach-by-ID cleanup to make in Kival at this point, since Kival does not currently persist application-owned Steda task IDs outside Steda’s own durable state.