Closed DeboMac closed 2 years ago
Yep, it makes more sense! Here is the PR with only source files modified
This line should easily reproduce the issue locally for a fix:
make drive3-cli-cargo ARGS=check
Note that it also builds the CLI which might not need to declare yup-oauth2 in its manifest either.
Thanks a lot, that works! Please let me know if there is any crate in particular that you'd like to see republished and it shall be done.
Thank you for being so responsive ! I'd love to see google-drive3 published, if it is doable !
You are welcome! Drive3 v2.0.9 was just released to crates.io and includes this fix.
Updating crates.io index
Packaging google-drive3 v2.0.9+20210322 (/Users/byron/dev/github.com/Byron/google-apis-rs/gen/drive3)
Verifying google-drive3 v2.0.9+20210322 (/Users/byron/dev/github.com/Byron/google-apis-rs/gen/drive3)
Compiling google-drive3 v2.0.9+20210322 (/Users/byron/dev/github.com/Byron/google-apis-rs/target/package/google-drive3-2.0.9+20210322)
Finished dev [unoptimized] target(s) in 2.97s
Uploading google-drive3 v2.0.9+20210322 (/Users/byron/dev/github.com/Byron/google-apis-rs/gen/drive3)
error: failed to publish to registry at https://crates.io
Caused by:
the remote server responded with an error (status 503 Service Unavailable): Crates.io is currently in read-only mode for maintenance. Please try again later.
Error: Could not successfully execute 'cargo publish'.
Turns out I will have to try again tomorrow.
And done, the new release is now available.
Fix #298