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

[PR #5634] ci: separate standalone publishing from dependent publishing #11505

New Issue
Closed
opened 2026-02-16 18:16:21 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:16:21 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/5634

State: closed
Merged: Yes

Now that the publish workflow keeps its release as a draft until the workflow completes, it's possible for a published package (eg brew, AUR) to reference a release that is currently drafted. To remedy, I've split up some of the publish process.

At a high level, the first job runs publish-start.ts, which publishes to npm, ghcr, and creates the draft release.
Next the desktop builds run, downloading the previously published CLI binaries from the draft release, and uploading their own assets to the release.
Lastly in publish-complete.ts the release is un-drafted, then the brew and AUR packages are published (since now the assets they reference are published).

The naming here and organisation of the scripts probably needs changing.

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/5634 **State:** closed **Merged:** Yes --- Now that the publish workflow keeps its release as a draft until the workflow completes, it's possible for a published package (eg brew, AUR) to reference a release that is currently drafted. To remedy, I've split up some of the publish process. At a high level, the first job runs `publish-start.ts`, which publishes to npm, ghcr, and creates the draft release. Next the desktop builds run, downloading the previously published CLI binaries from the draft release, and uploading their own assets to the release. Lastly in `publish-complete.ts` the release is un-drafted, then the brew and AUR packages are published (since now the assets they reference are published). The naming here and organisation of the scripts probably needs changing.
yindo added the pull-request label 2026-02-16 18:16:21 -05:00
yindo closed this issue 2026-02-16 18:16:21 -05:00
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 pull-request
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#11505
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?