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 and npm miss versionning 0.5.16 !! #1451

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

Originally created by @thegreyfellow on GitHub (Aug 22, 2025).

Originally assigned to: @thdxr on GitHub.

Both repos show 0.5.16, but the latest version is 0.5.15 .

AUR: https://aur.archlinux.org/packages/opencode-bin

Image

npm: https://www.npmjs.com/package/opencode-ai

Image

Guys is this normal ?!!

Originally created by @thegreyfellow on GitHub (Aug 22, 2025). Originally assigned to: @thdxr on GitHub. Both repos show 0.5.16, but the latest version is 0.5.15 . AUR: https://aur.archlinux.org/packages/opencode-bin <img width="286" height="134" alt="Image" src="https://github.com/user-attachments/assets/1aea342e-f62c-4c13-82fb-1901a53aee03" /> npm: https://www.npmjs.com/package/opencode-ai <img width="530" height="401" alt="Image" src="https://github.com/user-attachments/assets/4a2e04e6-2324-49b9-8c3f-fe1a665f7864" /> Guys is this normal ?!!
yindo closed this issue 2026-02-16 17:31:02 -05:00
yindo commented 2026-02-16 17:31:02 -05:00
Author
Owner
Copy Link
Copy Source

@omarzina commented on GitHub (Aug 22, 2025):

Something similar is happening with hombrew as well.

❯ brew upgrade opencode
==> Upgrading 1 outdated package:
sst/tap/opencode 0.5.13 -> 0.5.16
==> Fetching downloads for: opencode
==> Fetching sst/tap/opencode
==> Downloading https://github.com/sst/opencode/releases/download/v0.5.16/opencode-darwin-arm64.zip
curl: (56) The requested URL returned error: 404

Error: opencode: Failed to download resource "opencode (0.5.16)"
Download failed: https://github.com/sst/opencode/releases/download/v0.5.16/opencode-darwin-arm64.zip
==> No outdated dependents to upgrade!
@omarzina commented on GitHub (Aug 22, 2025): Something similar is happening with hombrew as well. ```sh ❯ brew upgrade opencode ==> Upgrading 1 outdated package: sst/tap/opencode 0.5.13 -> 0.5.16 ==> Fetching downloads for: opencode ==> Fetching sst/tap/opencode ==> Downloading https://github.com/sst/opencode/releases/download/v0.5.16/opencode-darwin-arm64.zip curl: (56) The requested URL returned error: 404 Error: opencode: Failed to download resource "opencode (0.5.16)" Download failed: https://github.com/sst/opencode/releases/download/v0.5.16/opencode-darwin-arm64.zip ==> No outdated dependents to upgrade! ```
yindo commented 2026-02-16 17:31:02 -05:00
Author
Owner
Copy Link
Copy Source

@ditwrd commented on GitHub (Aug 23, 2025):

tldr: split publish.ts into separate build.ts and publish.ts scripts to avoid half-published releases when builds fail

Hi @thdxr, I almost create an issue for this, but it seems @thegreyfellow got here first

There's been a few desync events lately in AUR, since it's bugging me a lot (jk), I skimmed through the pipeline scripts

Looks like the culprit is here:
https://github.com/sst/opencode/blob/3706b2bca7bb2e813391dad35a795fd03e36f905/script/publish.ts#L32-L39

Right now each script builds and publishes in one go, so the flow ends up like:
Build opencode --> Publish opencode --> Build sdk --> Publish sdk --> Build plugins --> Publish plugins --> Github Release

The issue is if a build fails midway, you get a half-published release
That's what happened in 0.5.16 (and any other release before):
https://github.com/sst/opencode/actions/runs/17167359455/job/48710548415

The sdk build failed, but by that point opencode was already published, so the flow looked like:
Build opencode --> Publish opencode --> 💀 Build sdk

No GitHub release was created, but the package was already out (in AUR and homebrew, hence the error from both @thegreyfellow and @omarzina)

Possible fix:
Split each publish.ts into two scripts — build.ts and publish.ts, that way the flow can be:

Build opencode --> Build sdk --> Build plugins --> Publish opencode --> Publish sdk --> Publish plugins --> Github Release

This way, if a build fails, nothing gets published and no release is created, but to be honest idk if there's any reason it was created that way in the first place so my possible "fix" might not cater with the initial requirements

I'm not a TypeScript dev, but work with pipelines daily, I can try putting together a PR to split publish.ts with some AI help if that helps

@ditwrd commented on GitHub (Aug 23, 2025): **tldr**: split `publish.ts` into separate `build.ts` and `publish.ts` scripts to avoid half-published releases when builds fail Hi @thdxr, I almost create an issue for this, but it seems @thegreyfellow got here first There's been a few desync events lately in AUR, since it's bugging me a lot (jk), I skimmed through the pipeline scripts Looks like the culprit is here: [https://github.com/sst/opencode/blob/3706b2bca7bb2e813391dad35a795fd03e36f905/script/publish.ts#L32-L39](https://github.com/sst/opencode/blob/3706b2bca7bb2e813391dad35a795fd03e36f905/script/publish.ts#L32-L39) Right now each script builds *and* publishes in one go, so the flow ends up like: **Build opencode --> Publish opencode --> Build sdk --> Publish sdk --> Build plugins --> Publish plugins --> Github Release** The issue is if a build fails midway, you get a half-published release That's what happened in 0.5.16 (and any other release before): [https://github.com/sst/opencode/actions/runs/17167359455/job/48710548415](https://github.com/sst/opencode/actions/runs/17167359455/job/48710548415) The sdk build failed, but by that point `opencode` was already published, so the flow looked like: Build opencode --> Publish opencode --> 💀 Build sdk No GitHub release was created, but the package was already out (in AUR and homebrew, hence the error from both @thegreyfellow and @omarzina) Possible fix: Split each `publish.ts` into two scripts — `build.ts` and `publish.ts`, that way the flow can be: **Build opencode --> Build sdk --> Build plugins --> Publish opencode --> Publish sdk --> Publish plugins --> Github Release** This way, if a build fails, nothing gets published and no release is created, but to be honest idk if there's any reason it was created that way in the first place so my possible "fix" might not cater with the initial requirements I'm not a TypeScript dev, but work with pipelines daily, I can try putting together a PR to split `publish.ts` with some AI help if that helps
yindo commented 2026-02-16 17:31:02 -05:00
Author
Owner
Copy Link
Copy Source

@ditwrd commented on GitHub (Aug 23, 2025):

Created a PR at #2201 for now, haven't tested it fully since sdk is failing to build and a bit out of scope for my yaml brain, but in theory this should work 🤞, at least that's what I hope for 👋

@ditwrd commented on GitHub (Aug 23, 2025): Created a PR at #2201 for now, haven't tested it fully since sdk is failing to build and a bit out of scope for my `yaml` brain, but in theory this should work 🤞, at least that's what I hope for 👋
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
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#1451
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?