Skip to content

fix: document message naming conventions - #209

Merged
achingbrain merged 2 commits into
mainfrom
fix/document-naming-conventions
Sep 18, 2026
Merged

achingbrain merged 2 commits into
mainfrom
fix/document-naming-conventions

Conversation

@achingbrain

Copy link
Copy Markdown
Member

Add a note to the readme about naming messages.

Fixes #64

Add a note to the readme about naming messages.

Fixes #64
@achingbrain
achingbrain merged commit c1e3bcb into main Sep 18, 2026
26 checks passed
@achingbrain
achingbrain deleted the fix/document-naming-conventions branch September 18, 2026 08:09
github-actions Bot pushed a commit that referenced this pull request Sep 18, 2026
## [protons-runtime-v8.0.1](protons-runtime-8.0.0...protons-runtime-8.0.1) (2026-09-18)

### Bug Fixes

* document message naming conventions ([#209](#209)) ([c1e3bcb](c1e3bcb)), closes [#64](#64)
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version protons-runtime-v8.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

github-actions Bot pushed a commit that referenced this pull request Sep 18, 2026
## [protons-v10.0.4](protons-10.0.3...protons-10.0.4) (2026-09-18)

### Bug Fixes

* document message naming conventions ([#209](#209)) ([c1e3bcb](c1e3bcb)), closes [#64](#64)
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version protons-v10.0.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Type name conflict when enum is named Error

1 participant