anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-21 17:56:33 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Too many releases, which version should be packaged? #2720

New Issue
Open
opened 2026-02-16 17:36:57 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 17:36:57 -05:00
Owner
Copy Link
Copy Source

Originally created by @bew on GitHub (Nov 9, 2025).

Originally assigned to: @thdxr on GitHub.

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
https://github.com/NixOS/nixpkgs/pull/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!

Originally created by @bew on GitHub (Nov 9, 2025). Originally assigned to: @thdxr on GitHub. ### 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 https://github.com/NixOS/nixpkgs/pull/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!
yindo added the opentui label 2026-02-16 17:36:57 -05:00
yindo commented 2026-02-16 17:36:57 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Nov 9, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #3739: Packaging Guidance Request for v1.x - specifically discusses packaging OpenCode for Nixpkgs and build challenges
  • #3540: make opencode work w/ NixOS - mentions that the nixpkgs version is extremely old and needs regular updates
  • #462: Add support for NixOS and/or Static linked binaries - also discusses packaging challenges for NixOS users

Feel free to ignore if none of these address your specific case about release frequency and version stability for packaging.

@github-actions[bot] commented on GitHub (Nov 9, 2025): This issue might be a duplicate of existing issues. Please check: - #3739: Packaging Guidance Request for v1.x - specifically discusses packaging OpenCode for Nixpkgs and build challenges - #3540: make opencode work w/ NixOS - mentions that the nixpkgs version is extremely old and needs regular updates - #462: Add support for NixOS and/or Static linked binaries - also discusses packaging challenges for NixOS users Feel free to ignore if none of these address your specific case about release frequency and version stability for packaging.
yindo commented 2026-02-16 17:36:57 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (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: https://github.com/sst/opencode/pull/3924

@rekram1-node commented on GitHub (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: https://github.com/sst/opencode/pull/3924
yindo commented 2026-02-16 17:36:57 -05:00
Author
Owner
Copy Link
Copy Source

@thdxr commented on GitHub (Nov 11, 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

@thdxr commented on GitHub (Nov 11, 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
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label opentui
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2720
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?