The cargo-publish-workspace from foresterre

cargo-publish-workspace's Introduction

Hello! I'm Martijn

^{【🐦 I'm a Software Engineer from The Netherlands. I love open source, software design and language engineering!】}

A selection of my open source projects:

	📦 Project	👐 Description
🦀	cargo-msrv	Find the minimum supported Rust version (MSRV) for your project
🦜	sic	Accessible image processing and conversion from the terminal. Front-end for image-rs/image.
🛬	rust-releases	Identify the officially available Rust releases
🎹	bisector	Flexible, stateless implementation of the bisection method
👀	peekmore	Multi-peek, no-std, iterator for Rust
🎙	storyteller	A library for working with user output
🐑	parameterized	JUnit style parameterized testing for Rust
🛶	yare	Lean parameterized testing library for Rust

And more:

rust-toolchain-file: Parser for rust-toolchain(.toml) files.
version-number: Semver(like)-lite, parsing two- and three component version numbers, such as the rust-version field in the Cargo Manifest.
sif: Yet another parameterized testing attribute macro 🥰
... all my public libraries and projects

cargo-publish-workspace's People

Contributors

Stargazers

Watchers

cargo-publish-workspace's Issues

Compilation error installing from crates.io

TLDR:

   Compiling cargo-publish-workspace v0.18.1
error[E0599]: no variant or associated item named `VersionlessSubcommands` found for enum `AppSettings` in the current scope
  --> /home/wycats/.cargo/registry/src/github.com-1ecc6299db9ec823/cargo-publish-workspace-0.18.1/src/arguments.rs:37:33
   |
37 |     global_setting(AppSettings::VersionlessSubcommands),
   |                                 ^^^^^^^^^^^^^^^^^^^^^^ variant or associated item not found in `AppSettings`

This doesn't happen when installing from git, and the code it points to is no longer in the codebase. Perhaps a semver-violating breaking change? Either way, it seems like it would be good to do another release.

Add option to retry

The update of the crates.io index fails relatively often. Instead of cancelling completely, requiring a manual restart and skipping already published crates, we should add an option which will retry the current crate, if the error is not fatal.

Recommend Projects