-
-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: force object type for message trait's headers #102
fix: force object type for message trait's headers #102
Conversation
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@derberg @fmvilas @magicmatatjahu any progress here? |
@jonaslagoni You dug up some dead PR 😅 I'll make an update for 2.2 and a separate PR for 2.3. |
08cbcf3
to
b34fce9
Compare
@derberg Could you check? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Let's wait for @derberg.
/dnm |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@magicmatatjahu feel free to merge it yourself :) |
/rtm |
🎉 This PR is included in version 2.13.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 3.0.0-next-major.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Force object type for message trait's headers in
2.0.0
,2.1.0
and2.2.0
versions.PR for
2.3.0
#155Related issue(s)
Fixes #82