[Request]: Can you make a release after the 1.82 fixes

[happysalada]

What did you expect to happen?

working package in nixpkgs

What happened?

the last release is broken with rust 1.82, that means that the package in nixpkgs is broken

Atuin doctor output

I completely realise that atuin is not at fault here. It would be nice to have another release, but no worries if you are busy.

Code of Conduct

• I agree to follow this project's Code of Conduct

[ellie]

Definitely looking to get a release out soon as it's been WAY too long, there's a couple of serverside adjustments I need to make to our deployment first though.

I'm a little concerned that the package in nix no longer builds though, surely all the deps are pinned?

[happysalada]

The deps are pinned, but only a single version of rustc is used to prevent dependency explosion, so right now on everything is on rust 1.82 and atuin doesnt compile on latest master. Its not a big deal, people on unstable know what they are signing for, but i just thought i might put a request for a new release.
No rush, take the time you need to do things right !

[eric-hansen]

It's bee na while since I had to deal w/ the Nix/Rust thing, but wouldn't either a devenv or devShell derivation solve the issue with compiling? could make it part of the preInstall build step (I think). Then just have a Rust input locked to a specific nixpkgs commit where the non-broken build can happen.

[happysalada]

The package failing is on nixpkgs, so you cant just use any rust version you have to use the one provided by nixpkgs.
Its not a major problem, the release will be appreciated when you have time.

[happysalada]

Friendly bump on making a new release