crush: 0.6.1 -> 0.7.4

[bendlas]

Things done

• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• Tested, as applicable:
  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Ran nixpkgs-review on this PR. See nixpkgs-review usage.
• Tested basic functionality of all binary files, usually in ./result/bin/.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

---

Add a 👍 reaction to pull requests you find important.

[MisileLab]

https://github.com/charmbracelet/crush/releases/tag/v0.7.1 released

[bendlas]

Oh, sorry, hadn't seen that you also had PR on. Updated to 0.7.1

[bendlas]

Kind of surpised on why we're getting a merge conflict here. Seems we caught a random stray from a revert.

Looking through 106b141 I really don't understand why crush should have been affected. I don't think it ever went through staging, nor does it use python. Also, the associated PR seems for something else entirely. The revert looks like many other unrelated packages could have been affected.

Few questions for @mweinelt:
Are you sure that the revert was scoped correctly?
Are there further irregularities incoming, or can/should we rebase and move on?
Is there any associated discussion/review/explaination, that could have been linked to the revert?
Is somebody making sure that we didn't downgrade many other unrelated packages?

[mweinelt]

Context is here: #432489 (comment)

Workflow: Inspected both parents of the merge and returned to the one that was staging-next, and not master. Then redid the merge without mergiraf.

[bendlas]

Workflow: Inspected both parents of the merge and returned to the one that was staging-next, and not master. Then redid the merge without mergiraf.

If the merge was re-done correctly, shouldn't then crush have stayed at 0.6.1? I don't even see the correct version in staging-next, so it looks like it just got lost.

Is somebody checking all the other affected packages?

[bendlas]

merge conflict has now been resolved

[MisileLab]

https://github.com/charmbracelet/crush/releases/tag/v0.7.2 released

[phanirithvij]

0.7.4 is the latest version

[MisileLab]

https://github.com/charmbracelet/crush/releases/tag/v0.7.5

[MisileLab]

https://github.com/charmbracelet/crush/releases/tag/v0.7.6

[bendlas]

I won't be updating this PR any longer, because I'm no longer interested in crush, after I learned that it's a commercial re-licensing of https://github.com/sst/opencode

Feel free to take any commit from this, if you decide to open another PR