Repository navigation
Too many releases, which version should be packaged? #4114
Description
Question
Hello!
There's attempts to package opencode in nixpkgs (for Nix users), but with the rate of releases it's really hard to decide which version to use.
As soon as we merge a version there's almost already a new version available...
For example 1.0.45 managed to get merged yesterday
NixOS/nixpkgs#459761
But today we're already at 1.0.51 😬
And given that it takes ~1-2 days to be available in nixpkgs-unstable branch, we'll always be somewhat late to the party..
Are you currently quickly working towards a feature-set that'll be mostly complete?
Aka: Is this release frenzy going to slow down anytime soon?
Is there a version (apart from 1.0.0 maybe) that you'd would say is pretty stable to package?
Or are packages supposed to be 'late' and behind real releases?
Is every release supposed to be packageable ?
Thank you!
Activity
github-actions commentedon Nov 9, 2025
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case about release frequency and version stability for packaging.
[-]Too many releases, which version should we package?[/-][+]Too many releases, which version should be packaged?[/+]rekram1-node commentedon Nov 9, 2025
@bew yeah we are doing a bit of a frenzy to address any new issues introduced by opentui migration
Someone has been working on packaging a nix flake tho: #3924
thdxr commentedon Nov 12, 2025
we'll also bump the minor soon and you can probably just stick to minors? not sure what the best approach is - realistically we can't guarantee we don't release several times a day