Skip to content

Conversation

gabrielbosio
Copy link

No description provided.

@gabrielbosio gabrielbosio marked this pull request as ready for review October 8, 2025 22:00
@xJonathanLEI
Copy link
Owner

I'm not sure about this. What's the rationale for the bump? Is there a security or other critical issues with <0.2.3? As a library crate we should stay as forgiving as possible in terms of crate version ranges.

@gabrielbosio
Copy link
Author

@xJonathanLEI I understand that it makes sense to keep types-rs in 0.2.0 but in this case we had to fix a performance regression related to Pedersen hashing (~120%) in 0.2 which introduced a breaking change. Given the context we had to make an exception regarding semver, that's why these changes were introduced in 0.2.3.

@dorimedini-starkware
Copy link

@gabrielbosio @xJonathanLEI I am fine with merging this or closing this without merging, as long as we have some 0.2.x version of types-rs we can compile with the 0.13.0 lambdaworks

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.

3 participants