Closed star-du closed 1 year ago
It's also mentioned in another issue in mdbook-svgbob
here , but sadly the discussion there was not immediately helpful to me.
Hi @star-du,
Thanks for reporting this! The full steps used when publishing new versions are found in install-mdbook/action.yml
:
cargo install mdbook --locked --version 0.4.28
cargo install mdbook-svgbob --locked --version 0.2.1
cargo install mdbook-i18n-helpers --locked --version 0.1.0
cargo install --path mdbook-exerciser --locked
I think you've basically discovered that we have a lurking incompatibility between the latest version of mdbook and mdbook-svgbob. We don't notice in CI since we lock the version, but we would definitely need to debug this.
I think we're seeing https://github.com/rust-lang/mdBook/issues/2019 again — bumping the toml dependency in mdbook causes the plugins to fail.
This was fixed quickly by rolling back the change in mdbook — I just checked and I can compile things fine with mdbook 0.4.34.
Sorry I was out of town last two weeks. Thanks @mgeisler for the response and I'm glad if this issue helps the team : )
I follow the instruction to install
mdbook
andmdbook-svgbob
in README. However, as of today (July 29th), when I runcargo install mdbook mdbook-svgbob
, it reports:It seems this version of
mdbook-svgbob
does not like mymdbook v0.4.32
, which is the version in crates.io registry.I see we are using
--locked
flag in.github/workflows/install-mdbook/action.yml
to specify the desired mdbook version (v0.4.28), which works for me. Should we update the README.md as well, so new users will not be frustrated by similar build failures?