anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

AUR version always incremented by 1 #3692

New Issue
Closed
opened 2026-02-16 17:41:07 -05:00 by yindo · 7 comments
yindo commented 2026-02-16 17:41:07 -05:00
Owner
Copy Link
Copy Source

Originally created by @furai on GitHub (Dec 20, 2025).

Originally assigned to: @thdxr on GitHub.

Description

I'm not sure what exactly the issue is but it seems that publishing the aur package relies on published version in npm registry which is later incremented by 1. This breaks AUR releases as it always refers to "future" release. Maybe the order of workflows changed and now first npm is published then version for AUR is generated which will be higher than expected by 1?

I haven't had time to dig deeper. I hope my investigation helps someone with fixing the issue correctly.

CC: @thdxr

OpenCode version

1.0.176

Steps to reproduce

  1. Try to install opencode from AUR.
  2. Fail.

Screenshot and/or share link

No response

Operating System

Arch Linux

Terminal

No response

Originally created by @furai on GitHub (Dec 20, 2025). Originally assigned to: @thdxr on GitHub. ### Description I'm not sure what exactly the issue is but it seems that publishing the aur package relies on published version in npm registry which is later incremented by 1. This breaks AUR releases as it always refers to "future" release. Maybe the order of workflows changed and now first npm is published then version for AUR is generated which will be higher than expected by 1? I haven't had time to dig deeper. I hope my investigation helps someone with fixing the issue correctly. CC: @thdxr ### OpenCode version 1.0.176 ### Steps to reproduce 1. Try to install opencode from AUR. 2. Fail. ### Screenshot and/or share link _No response_ ### Operating System Arch Linux ### Terminal _No response_
yindo added the bug label 2026-02-16 17:41:07 -05:00
yindo closed this issue 2026-02-16 17:41:07 -05:00
yindo commented 2026-02-16 17:41:08 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Dec 20, 2025):

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

  • #3784: Relese version mismatch in AUR v1.0.14-1 (AUR package showing incorrect/mismatched version numbers)
  • #2189: AUR and npm miss versionning 0.5.16 (version discrepancy between AUR and npm registry)

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Dec 20, 2025): This issue might be a duplicate of existing issues. Please check: - #3784: Relese version mismatch in AUR v1.0.14-1 (AUR package showing incorrect/mismatched version numbers) - #2189: AUR and npm miss versionning 0.5.16 (version discrepancy between AUR and npm registry) Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:41:08 -05:00
Author
Owner
Copy Link
Copy Source

@furai commented on GitHub (Dec 20, 2025):

It looks similar to #2189. I didn't see it when creating the issue as it was closed already.

@furai commented on GitHub (Dec 20, 2025): It looks similar to #2189. I didn't see it when creating the issue as it was closed already.
yindo commented 2026-02-16 17:41:08 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 20, 2025):

this only started happening last night becase of a publish issue

anyways should be fixed now

@rekram1-node commented on GitHub (Dec 20, 2025): this only started happening last night becase of a publish issue anyways should be fixed now
yindo commented 2026-02-16 17:41:08 -05:00
Author
Owner
Copy Link
Copy Source

@gwuen commented on GitHub (Dec 20, 2025):

this only started happening last night becase of a publish issue

The AUR package pointing to a release not (yet) published on GitHub has been a common occurrence over multiple months now. This really does look like #2189. Are you sure this is fixed now?

@gwuen commented on GitHub (Dec 20, 2025): > this only started happening last night becase of a publish issue The AUR package pointing to a release not (yet) published on GitHub has been a common occurrence over multiple months now. This really does look like #2189. Are you sure this is fixed now?
yindo commented 2026-02-16 17:41:08 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 20, 2025):

I see 180 on both?

The reason it broke is because the release script got reworked, and had cascading failures which were then fixed this morning, now if it has happened in the past to you im assumingit was the same thing

But i think dax has it in a better state now so itll bemore resilient in the future

@rekram1-node commented on GitHub (Dec 20, 2025): I see 180 on both? The reason it broke is because the release script got reworked, and had cascading failures which were then fixed this morning, now if it has happened in the past to you im assumingit was the same thing But i think dax has it in a better state now so itll bemore resilient in the future
yindo commented 2026-02-16 17:41:08 -05:00
Author
Owner
Copy Link
Copy Source

@gwuen commented on GitHub (Dec 20, 2025):

I see 180 on both?

Yes, right now it looks alright. I also didn't mean to say it was always broken in the past, just occasionally it pointed to an unavailable newer release.

My guess is that the publish workflow pushes to the AUR before the release is made available on GitHub, or it breaks in-between these steps. #2201 promises to fix exactly this, but it's not merged yet.

If you say this should be fixed now, let's just wait and see if it works reliably now.

@gwuen commented on GitHub (Dec 20, 2025): > I see 180 on both? Yes, right now it looks alright. I also didn't mean to say it was *always* broken in the past, just occasionally it pointed to an unavailable newer release. My guess is that the `publish` workflow pushes to the AUR before the release is made available on GitHub, or it breaks in-between these steps. #2201 promises to fix exactly this, but it's not merged yet. If you say this should be fixed now, let's just wait and see if it works reliably now.
yindo commented 2026-02-16 17:41:08 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 20, 2025):

Yeah that makes more sense then haha, if it continues to happen lmk and i will look into a more reliable method.

We keep trying to make things more reliable and since we added desktop app it complicates the releases even more so some stuff got bugged yesterday

@rekram1-node commented on GitHub (Dec 20, 2025): Yeah that makes more sense then haha, if it continues to happen lmk and i will look into a more reliable method. We keep trying to make things more reliable and since we added desktop app it complicates the releases even more so some stuff got bugged yesterday
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 bug
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#3692
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?