[
https://issues.apache.org/jira/browse/THRIFT-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18092646#comment-18092646
]
Jens Geyer commented on THRIFT-6074:
------------------------------------
Official release is the exact point. there are no unofficial releases and
0.24.0 is not yet released.
https://www.apache.org/legal/release-policy.html#what
> Publish Rust thrift 0.24.0 crate to crates.io
> ---------------------------------------------
>
> Key: THRIFT-6074
> URL: https://issues.apache.org/jira/browse/THRIFT-6074
> Project: Thrift
> Issue Type: Task
> Components: Rust - Library
> Reporter: Santiago Medina
> Priority: Major
>
> The Rust library version in master (lib/rs/Cargo.toml) is 0.24.0, but the
> latest `thrift` crate on crates.io is 0.23.0. Downstream Rust projects
> therefore can't depend on the 0.24.0 features already in master:
> - the `crate_prefix` generator option (emitting generated code into a
> `src/thrift/` submodule),
> - `list<union>` code generation,
> - union / length-prefix parsing robustness fixes.
> Today such consumers must pin a git revision via `[patch.crates-io]`, which
> cannot be published transitively.
> Per lib/rs/RELEASING.md ("Any thrift project committer is allowed to upload a
> new crate"), this is a Rust-only crate publish independent of a full
> multi-language release. Request: publish `thrift` 0.24.0 to crates.io from
> current master. Steps are in lib/rs/RELEASING.md (`cargo package` +
> `cargo publish`).
> Note: crates.io versions are immutable, so once 0.24.0 is published the
> eventual official 0.24.0 release's `release_rust.yml` step should treat it as
> already-published.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
