Skip to content

fix: Describe the signing key of the test container as what it is. - #407

Merged
goloroden merged 1 commit into
mainfrom
fix-signing-key-description
Sep 26, 2026
Merged

goloroden merged 1 commit into
mainfrom
fix-signing-key-description

Conversation

@goloroden

Copy link
Copy Markdown
Member

The README said that the signing key can be used when configuring the container to sign outgoing events, which the SDK does not offer. It now describes the signing key as what it is: the private key EventSourcingDB signs events with. The same wording is used in all SDKs now.

This is a fix, so that the registry shows the corrected README, too.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VVZx93wLHrp5dyCWKjUAfd

The README said that the signing key can be used when configuring the
container to sign outgoing events, which the SDK does not offer. It is the
private key EventSourcingDB signs events with.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VVZx93wLHrp5dyCWKjUAfd
@goloroden
goloroden requested a review from a team as a code owner September 26, 2026 11:09
@goloroden goloroden self-assigned this Sep 26, 2026
@goloroden
goloroden merged commit 21b0cf8 into main Sep 26, 2026
2 checks passed
@goloroden
goloroden deleted the fix-signing-key-description branch September 26, 2026 11:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant