chore: repoint distribution from GitHub to the forge #1

Merged

mph merged 1 commit from forge/repoint-distribution into main

2026-07-28 17:24:31 +00:00

mph commented

2026-07-28 11:41:43 +00:00

Owner

Summary

claude-jvm-proxy now lives on the forge. This repoints its public distribution surface off GitHub:

install.sh — the jvm-proxy binary now downloads from the forge release (code.iterative.works/.../releases/download/vX.Y.Z/...).
README.md — both curl bootstrap lines now use the forge raw URL.

Notes

Forgejo has no releases/latest/download/ alias (GitHub does), so the binary version is pinned via JVM_PROXY_VERSION (currently 0.2.0) — bump it on each release. This mirrors the existing SCALA_CLI_VERSION pin in the same script.
The VirtusLab/scala-cli download URL is a third-party upstream and is left unchanged.
Release binaries (v0.1.0, v0.2.0, jvm-proxy-linux-x86_64) were carried over by the server-side migrate and resolve anonymously from the forge.

Not in this PR (deliberate)

Release automation. Only jvm-proxy-linux-x86_64 has ever shipped (the macOS/aarch64 branches in install.sh were never built). Automating that single build on the forge runner needs a Scala Native toolchain (clang/LLVM) whose availability in the runner container is unverified — tracked separately so this repoint isn't blocked on it.

🤖 Generated with Claude Code

## Summary `claude-jvm-proxy` now lives on the forge. This repoints its public distribution surface off GitHub: - **`install.sh`** — the `jvm-proxy` binary now downloads from the forge release (`code.iterative.works/.../releases/download/vX.Y.Z/...`). - **`README.md`** — both `curl` bootstrap lines now use the forge raw URL. ## Notes - Forgejo has no `releases/latest/download/` alias (GitHub does), so the binary version is **pinned** via `JVM_PROXY_VERSION` (currently `0.2.0`) — bump it on each release. This mirrors the existing `SCALA_CLI_VERSION` pin in the same script. - The `VirtusLab/scala-cli` download URL is a third-party upstream and is left unchanged. - Release binaries (`v0.1.0`, `v0.2.0`, `jvm-proxy-linux-x86_64`) were carried over by the server-side migrate and resolve anonymously from the forge. ## Not in this PR (deliberate) - **Release automation.** Only `jvm-proxy-linux-x86_64` has ever shipped (the macOS/aarch64 branches in `install.sh` were never built). Automating that single build on the forge runner needs a Scala Native toolchain (clang/LLVM) whose availability in the runner container is unverified — tracked separately so this repoint isn't blocked on it. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

mph added 1 commit

2026-07-28 11:41:44 +00:00

chore: repoint distribution from GitHub to the forge ac304bfca6

Point the install bootstrap and README at code.iterative.works now that
the canonical repo lives on the forge. The forge has no
releases/latest/download alias, so pin JVM_PROXY_VERSION (bump on release).
The VirtusLab scala-cli download URL is upstream and left unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

mph merged commit 02150c763f into main

2026-07-28 17:24:31 +00:00

mph deleted branch forge/repoint-distribution

2026-07-28 17:24:31 +00:00

mph referenced this pull request from a commit

2026-07-28 17:24:32 +00:00

Merge pull request 'chore: repoint distribution from GitHub to the forge' (#1) from forge/repoint-distribution into main