binary releases and mise tool #62

New issue

Closed

opened 2026-02-05 21:28:08 +00:00 by choucavalier · 2 comments

choucavalier commented

2026-02-05 21:28:08 +00:00

(Migrated from codeberg.org)

thanks a lot for working on this! really cool :)

it seems that binary releases are not available even though they are mentioned in the README

also it would be cool if the binary would be packaged in mise.jdx.dev (mise use -g forgejo-mcp)

thanks a lot for working on this! really cool :) it seems that binary releases are not available even though they are mentioned in the README also it would be cool if the binary would be packaged in mise.jdx.dev (`mise use -g forgejo-mcp`)

choucavalier commented

2026-02-05 21:30:24 +00:00

(Migrated from codeberg.org)

(note that releasing binaries on codeberg would make it available in mise via the forgejo backend)

(note that releasing binaries on codeberg would make it available in mise [via the forgejo backend](https://mise.jdx.dev/dev-tools/backends/forgejo.html))

goern commented

2026-02-06 08:19:15 +00:00

(Migrated from codeberg.org)

The release workflow has been fixed in main — it was using the wrong runner label (ubuntu-latest instead of codeberg-tiny) and the binary names were still using the old mcp-gitea prefix.

Changes pushed:

Runner: codeberg-tiny (matches Codeberg's infrastructure)
Binary naming: forgejo-mcp-{version}-{os}-{arch}
Static builds with CGO_ENABLED=0
Tag filter restricted to v* tags

Note: The workflow requires a RELEASE_TOKEN secret configured in the repo settings (Settings → Actions → Secrets) with write:repository scope. Binary releases should start appearing with the next tagged version.

Once releases are published, mise should pick them up automatically via its Forgejo backend.

The release workflow has been fixed in `main` — it was using the wrong runner label (`ubuntu-latest` instead of `codeberg-tiny`) and the binary names were still using the old `mcp-gitea` prefix. Changes pushed: - Runner: `codeberg-tiny` (matches Codeberg's infrastructure) - Binary naming: `forgejo-mcp-{version}-{os}-{arch}` - Static builds with `CGO_ENABLED=0` - Tag filter restricted to `v*` tags **Note:** The workflow requires a `RELEASE_TOKEN` secret configured in the repo settings (Settings → Actions → Secrets) with `write:repository` scope. Binary releases should start appearing with the next tagged version. Once releases are published, `mise` should pick them up automatically via its [Forgejo backend](https://mise.jdx.dev/dev-tools/backends/forgejo.html).

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

agentic-forges/forgejo-mcp#62

No description provided.

Rows
Columns