You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just updated zitadel-rust in one of my projects from v5.3.1 to v5.3.2. This lead to my code not compiling because the struct AddOidcAppRequest now has the field back_channel_logout_uri.
My guess is that the generated code was generated for the new version of zitadel and the changelog and version increment is just for the human made changes in this project.
I propose yanking v5.3.2 and making a new release with a semver compatible version number.
I think this project could benefit from being split into two crates with one being only the generated code and the other being a wrapper for it. This is in line with how many of the FFI-crates work.
The text was updated successfully, but these errors were encountered:
Hello,
I just updated
zitadel-rust
in one of my projects from v5.3.1 to v5.3.2. This lead to my code not compiling because the structAddOidcAppRequest
now has the fieldback_channel_logout_uri
.I think this was added in zitadel with version 2.65.0 https://github.com/zitadel/zitadel/releases/tag/v2.65.0
My guess is that the generated code was generated for the new version of zitadel and the changelog and version increment is just for the human made changes in this project.
I propose yanking v5.3.2 and making a new release with a semver compatible version number.
I think this project could benefit from being split into two crates with one being only the generated code and the other being a wrapper for it. This is in line with how many of the FFI-crates work.
The text was updated successfully, but these errors were encountered: