When trying to install the newest version via

cargo install cargo-shuttle

, I get the following compile error:

error[E0308]: mismatched types
  --> /home/glitch/.cargo/registry/src/github.com-1ecc6299db9ec823/shuttle-common-0.17.0/src/models/error.rs:27:43
   |
27 |             self.message.to_string().with(Color::Red)
   |                                      ---- ^^^^^^^^^^ expected `crossterm::style::Color`, found `comfy_table::Color`   |                                      |
   |                                      arguments to this method are incorrect
   |
   = note: `comfy_table::Color` and `crossterm::style::Color` have similar names, but are actually distinct types
note: `comfy_table::Color` is defined in crate `crossterm`
  --> /home/glitch/.cargo/registry/src/github.com-1ecc6299db9ec823/crossterm-0.26.1/src/style/types/color.rs:28:1
   |
28 | pub enum Color {
   | ^^^^^^^^^^^^^^
note: `crossterm::style::Color` is defined in crate `crossterm`
  --> /home/glitch/.cargo/registry/src/github.com-1ecc6299db9ec823/crossterm-0.25.0/src/style/types/color.rs:28:1
   |
28 | pub enum Color {
   | ^^^^^^^^^^^^^^
   = note: perhaps two different versions of crate `crossterm` are being used?
note: method defined here
  --> /home/glitch/.cargo/registry/src/github.com-1ecc6299db9ec823/crossterm-0.25.0/src/style/stylize.rs:78:8
   |
78 |     fn with(self, color: Color) -> Self::Styled {

Copy pasting from the feedback channel: Could be some dependency that broke semver perhaps? Try installing with binstall or with --locked.

Yeah, external semver breakage is very likely. I completely forgot about

--locked

, thanks!

out of curiosity, what does --locked do?

Locks the dependencies

If shuttle has a dependency on

abc="1.0.0"

(in its lock file) but abc 1.1.0 has been released, installing without locked mode would grab 1.1.0. If that update had a breaking change, you would end up with a "too new" version. --locked makes you use exactly the version in the lock file.

If I get time over the weekend I'll address the issues since obviously, not being able to install is kinda bad

The best solution would be to just file a report to

comfy_table

and get them to yank their

6.2.0

release

I'll file a gh issue. Hopefully it won't have been an intentional break

Seems like they just merged a dependabot PR. Probably on accident

Depends on if the project has good CI, but yeah

if with

--locked

is the only way to guarantee the installation is going to build... shouldnt that be the default? or am i misunderstanding something

If you want the latest version you don't use

--locked

- however this kind of issue while rare, can happen which is why this is the solution. It's just unfortunate because it's a Friday evening 💀

It assumes the community follows semver and only upgrades non-breaking patches. But yeah, with more power comes more responsibility

posted a gh issue on the repo - we just have to wait and see now

there is one already

that was me

aha, I thought you meant shuttle repo

i think im the one that made the shuttle repo one

ah - no I posted an issue on comfy-table's repo, just praying they come back soon lol

ah ye thats me

It's good for visibility

indeed

yeah definitely

Yes, it is a conflict, but it must have been triggered by a non semver-breaking patch upstream, right?

so in theory the fix would just be upgrading to crossterm .26?

I think there are lots of breaking changes in that version bump, so it might not

I had a look and it doesn't look like there are that many - the main issue is that there's nobody with write access on who can merge PRs at the moment

is this a good first issue tho? 👀

Don't see why not

been meaning to contribute to open source but havent yet... this could be my first. i'll give it a shot later today if no-one's done it by then

Yeah, but that's still a semver breaking change. They consciously tied their versioning to crossterm's, where a 0.x release is an incompatible one, by exposing them in their public API

Hmmmm, yeah I guess

Gave my two cents in your issue, but if everyone upgrades and no one complains, was it really breaking?