crates.io out of date

@0xb002f0 Is there a specific fix or feature you’re looking for in the next release?

@0xb002f0 Is there a specific fix or feature you’re looking for in the next release?

@0xb002f0 Is there a specific fix or feature you’re looking for in the next release?

@0xb002f0 Is there a specific fix or feature you’re looking for in the next release?

I'm specifically interested in the Ord implementations added by this PR

I'm specifically interested in the Ord implementations added by this PR

I'm specifically interested in the Ord implementations added by this PR

I'm specifically interested in the Ord implementations added by this PR

@TimonPost Any chance you could cut a new release?

@TimonPost Any chance you could cut a new release?

@TimonPost Any chance you could cut a new release?

@TimonPost Any chance you could cut a new release?

Would be great to have a release out.

Would be great to have a release out.

Would be great to have a release out.

Hi there, i'll see what i can do, missed this thread.

Hi there, i'll see what i can do, missed this thread.

If possible, is it possible to increase the number of administrators for crossterm on crates.io, or to set up trusted publishing? Would that allow other maintainers to create releases?

If possible, is it possible to increase the number of administrators for crossterm on crates.io, or to set up trusted publishing? Would that allow other maintainers to create releases?

I have granted some contributors access but crossterm. Have not heard of trusted publishing yet, I would be perfectly fine if other folks would want to publish a release once in a while. Good to keep it uptodated.

I have granted some contributors access but crossterm. Have not heard of trusted publishing yet, I would be perfectly fine if other folks would want to publish a release once in a while. Good to keep it uptodated.

@TimonPost Any update on this? crossterm is very widely used, and I think there are people like #1068 who are eagerly awaiting a release. Thank you!

I've been meaning to write up a good release approach for Crossterm for some time. Normally I'd use release-plz, but I don't think that's quite the right approach here yet, mostly because of the current CI setup and the relationship with crossterm-winapi.

I know people have been waiting a while for a release. I'm talking with Timon about how to handle the release-management side of that. Before setting up publishing, I want to do the CI cleanup that's been on my list for a while: modernize the existing workflow and improve the platform, feature, MSRV and packaging coverage. I'll follow that with a separate release-workflow proposal.

Release tooling is only part of the wait, though. Reviews are generally the limiting factor, so if you'd like to help get the next release out, please take a look at the open PRs. Testing one on your platform, checking that the docs make sense, or leaving questions and feedback is useful even if you don't know the whole codebase.

Bevy has an interesting approach where anyone can review PRs and community reviews help get changes ready for a final maintainer pass. Something similar might work well here. There's a good write-up, their review policy, and a talk about it if you're interested.

Fun fact: the reason I got involved in Ratatui and from there Crossterm in the first place was a sort of "take a penny, leave a penny" thing - I wanted a PR of mine reviewed, so figured it was only fair that I review some other PRs in the repo.