build(deps): upgrade crossterm to 0.27

[a-kenji]

Changelog

Upgrade crossterm to v0.27.

I don't think this is a breaking change, since the crossterm internals aren't exposed, is that correct?

[codecov]

Codecov Report

Merging #380 (b905805) into main (c8ddc16) will increase coverage by 0.02%.
Report is 1 commits behind head on main.
The diff coverage is 0.00%.

❗ Current head b905805 differs from pull request most recent head e7a7ac3. Consider uploading reports for the commit e7a7ac3 to get more accurate results

@@            Coverage Diff             @@
##             main     #380      +/-   ##
==========================================
+ Coverage   84.99%   85.02%   +0.02%     
==========================================
  Files          40       40              
  Lines        8686     8683       -3     
==========================================
  Hits         7383     7383              
+ Misses       1303     1300       -3     

Files Changed	Coverage Δ
src/backend/crossterm.rs	0.00% <0.00%> (ø)

[sayanarijit]

IMO it is a breaking change because ratatui requires us to install crossterm separately for input handling. Some extensions will break too.

[a-kenji]

You should be able to have ratatui with 0.27 and a separate crossterm for handling input events that is on 0.26.

And there shouldn't be conflicting dependencies since ratatui is not using the event feature.

Can you show me an example of an extension that will break as a result of this change?

I am happy to mark this as a breaking change if that is the consensus.

[joshka]

What should we do about doc comments / readme for this? Make the change now or leave it until we release? I wonder how many people use the version number from the github readme.

[a-kenji]

Thank you, that is a good point. I will update the references as well.

What should we do about doc comments / readme for this?

Since the version number is only in a doc comment I don't think it matters in this case.

Edit:
I think we should add bumping it on release to the RELEASE.md, since we don't know to which version the next release will be bumped.

[sayanarijit]

Cool... I have tested with tui-input. After a cargo update, works fine.

[a-kenji]

Thank you for testing it!

[orhun]

I remember Florian creating releases for only crossterm updates but I'm not sure if it is because he wanted to make the upgrade easier for the users or not. Just my 2 cents.

[a-kenji]

I remember Florian creating releases for only crossterm updates but I'm not sure if it is because he wanted to make the upgrade easier for the users or not.

I just looked through the releases of tui-rs.
It seems to me that only the last releases were specifically dependency bumps. When he was doing a release he also bumped dependencies. But more often crossterm itself was updated and what seems to me didn't influence the release schedule itself.