GitHub user tisonkun added a comment to the discussion: proposal: Release OpenDAL Components Seperately
While IIRC Cargo doesn't read build metadata at all, I'd refer to Protobuf's version strategy where they can introduce breaking changes for specific languages implementation - https://protobuf.dev/support/version-support/. The protobuf core remains using "feature.patch" pattern but it may not be suitable for OpenDAL Rust core. However, as you state "Node.js completely ignores them" and it can be a more complicated issue, while I suppose Java (Maven) just ignore the semantic but treat the version string as a literal so it happens to work. We may leave the discussion open for a while and highlight these challenges. Before we meet a real requirement to split the version we can use a synchronized version number for all bindings & core for now. GitHub link: https://github.com/apache/opendal/discussions/4126#discussioncomment-8355596 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
