fMeow
fMeow
Put this in your Cargo.toml should do. ```toml [patch.crates-io] jetscii = "0.5.3" ```
I find myself successfully compiling the docx using rust 1.63.0 on stable channel. Please try upgrade your cargo (`rustup udpate`) and update your dependencies (`cargo update`). If the issue still...
Sounds good. I suggest match against `refs/tags/` and create a new `publish` workflow which requires [manual trigger](https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow).
I personllay think to safer to run through all test before publish. But might clean the publish workflow to publish related pipeline only.
AFAIK 0.6.0 is not released to crates.io yet. So I don't think it necessary to bump a minor version.
I would recommend a automatic flow to publish commit with version tag to crates.io, which can be realized by github action. I would draft a PR and wait for the...
I have submit PR #53, which add publish section in github action. The only missing piece is a correct CARGO_TOKEN provided and configured by @moriturus in action secrets in repo...
There is nothing we can do about incompatible async runtime. But in this specific case, I think it can be resolved by upgrading mongodb to 2.0.0 or above, which depends...
I'm confused. ```rust #[maybe_async::test( feature="blocking", async(feature = "async", tokio::test) )] async fn test_oauth() { ``` The method `test_oauth` compiles on condition that feature "blocking" is enabled. And I assume feature...
fixed in v0.5.1