Fix Forgejo turbo-cache start-server action resolution #283

New issue

Closed

opened 2026-06-04 23:17:00 +00:00 by steve · 0 comments

steve commented

2026-06-04 23:17:00 +00:00

Owner

The macOS build-macos job in .forgejo/workflows/release-desktop.yml fails during Start Turbo remote cache because Forgejo resolves brunojppb/turbo-cache-server@4.0.7 against data.forgejo.org instead of GitHub.

Problem

Forgejo prepends DEFAULT_ACTIONS_URL (https://data.forgejo.org) to bare action references. The composite action .github/actions/turbo-remote-cache/start-server uses uses: brunojppb/turbo-cache-server@4.0.7, which Forgejo tries to clone from https://data.forgejo.org/brunojppb/turbo-cache-server and fails with remote: Not found.

Goal

Make the macOS desktop release job start the turbo remote cache without relying on Forgejo's default action registry.

Scope

.github/actions/turbo-remote-cache/start-server/action.yml

Non-goals

Changing Linux service-container turbo cache setup (already uses ghcr.io/... image directly).
Instance-level DEFAULT_ACTIONS_URL configuration.

Acceptance Criteria

start-server references brunojppb/turbo-cache-server@4.0.7 with a fully qualified GitHub URL so Forgejo clones from GitHub.
GitHub Actions workflows continue to work unchanged.

Implementation Notes

Use uses: https://github.com/brunojppb/turbo-cache-server@4.0.7 per Forgejo Actions docs for external third-party actions not mirrored on data.forgejo.org.

Suggested Files or Specs To Inspect

.github/actions/turbo-remote-cache/start-server/action.yml
.forgejo/workflows/release-desktop.yml (build-macos job)

Validation Commands

Review workflow/action YAML; no package checks required.

Follow-up to #274 — Wire Turborepo remote cache to Cloudflare R2 in CI

Follow-up Tasks

Implementation Summary

Pointed start-server at https://github.com/brunojppb/turbo-cache-server@4.0.7 so Forgejo clones from GitHub instead of data.forgejo.org.

The macOS `build-macos` job in `.forgejo/workflows/release-desktop.yml` fails during **Start Turbo remote cache** because Forgejo resolves `brunojppb/turbo-cache-server@4.0.7` against `data.forgejo.org` instead of GitHub. ## Problem Forgejo prepends `DEFAULT_ACTIONS_URL` (`https://data.forgejo.org`) to bare action references. The composite action `.github/actions/turbo-remote-cache/start-server` uses `uses: brunojppb/turbo-cache-server@4.0.7`, which Forgejo tries to clone from `https://data.forgejo.org/brunojppb/turbo-cache-server` and fails with `remote: Not found`. ## Goal Make the macOS desktop release job start the turbo remote cache without relying on Forgejo's default action registry. ## Scope - `.github/actions/turbo-remote-cache/start-server/action.yml` ## Non-goals - Changing Linux service-container turbo cache setup (already uses `ghcr.io/...` image directly). - Instance-level `DEFAULT_ACTIONS_URL` configuration. ## Acceptance Criteria 1. `start-server` references `brunojppb/turbo-cache-server@4.0.7` with a fully qualified GitHub URL so Forgejo clones from GitHub. 2. GitHub Actions workflows continue to work unchanged. ## Implementation Notes Use `uses: https://github.com/brunojppb/turbo-cache-server@4.0.7` per Forgejo Actions docs for external third-party actions not mirrored on `data.forgejo.org`. ## Suggested Files or Specs To Inspect - `.github/actions/turbo-remote-cache/start-server/action.yml` - `.forgejo/workflows/release-desktop.yml` (`build-macos` job) ## Validation Commands - Review workflow/action YAML; no package checks required. ## Related Issues - Follow-up to #274 — [Wire Turborepo remote cache to Cloudflare R2 in CI](../closed/274-wire-turborepo-remote-cache-to-cloudflare-r2-in-ci.md) ## Follow-up Tasks ## Implementation Summary Pointed start-server at https://github.com/brunojppb/turbo-cache-server@4.0.7 so Forgejo clones from GitHub instead of data.forgejo.org.

steve

2026-06-04 23:17:00 +00:00