-
Notifications
You must be signed in to change notification settings - Fork 196
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
[Merged by Bors] - SPU: Apply SmartModule Transformation For Producer #3014
Conversation
06b2985
to
575b00c
Compare
4b6188d
to
0d0b45e
Compare
6b5ffed
to
b93ebda
Compare
a8a3581
to
8072b30
Compare
I think the next set of failures are due to the DEV spu trying to decode smartmodule invocations that the STABLE cli doesn't send. I'll have to tinker with the versioning so that the new spu version can support older cli versions. |
I think that this comment will help you #3014 (comment) |
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.
Great job! Thanks for your contribution. Just a couple of minor fixes that are needed to be done before the merge.
f404c29
to
03bb8bb
Compare
03bb8bb
to
9bd75c3
Compare
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.
Looks good. Just have a minor request
crates/fluvio-protocol/Cargo.toml
Outdated
@@ -1,7 +1,7 @@ | |||
[package] | |||
name = "fluvio-protocol" | |||
edition = "2021" | |||
version = "0.9.0" | |||
version = "0.10.0" |
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.
Don't think this need major bump since we are only adding new API?
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.
My understanding is that what I did here is a minor bump.
I think you are right though. The SemVer docs say once the major version is >0, API additions require a minor version bump.
But since the major version is still 0, I think it is still subjective. I can change these all to only increment the patch value instead, if you like.
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.
Yes, let's change to only patch version which should minimize impact to downstream crates
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.
Everything looks ok except need to bump major version. Can you check if they are really needed or just need patch version upgrade if just adding fields or API
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.
Great work. LGTM
bors r+ |
Thanks! |
Build failed: |
Build failure in windows. Enable windows job and fix |
bors r+ |
Pull request successfully merged into master. Build succeeded: |
#2988