Add Forgejo Actions CI and release workflows #1

Merged
Lemarkis merged 7 commits from ci/forgejo-actions-setup into main 2026-09-09 20:10:44 +00:00
Owner

Adds .forgejo/workflows/ci.yml (runs on every PR, meant to become a required status check) and release.yml (builds .msi + arm64 .deb on a vX.Y.Z tag, publishes to a Forgejo release). Opening this PR mainly to verify ci.yml actually runs on the existing docker runner.

Adds .forgejo/workflows/ci.yml (runs on every PR, meant to become a required status check) and release.yml (builds .msi + arm64 .deb on a vX.Y.Z tag, publishes to a Forgejo release). Opening this PR mainly to verify ci.yml actually runs on the existing docker runner.
Add Forgejo Actions CI and release workflows
Some checks failed
CI / frontend (pull_request) Failing after 38s
CI / backend (pull_request) Failing after 37s
36bb9df273
CI (ci.yml): runs on every PR against main - frontend (npm check + test)
and backend (cargo test, with the Linux system deps needed to compile the
tauri crate) on the "docker" runner. Meant to become a required status
check on main once verified working.

Release (release.yml): on a vX.Y.Z tag push, builds a Windows .msi and a
Linux arm64 .deb (Tauri) and publishes both to a Forgejo release via the
REST API using the auto-provided FORGEJO_TOKEN. The windows/rockchip
runner labels don't exist yet, so those two jobs will sit queued until
matching runners are registered.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012rTfG1xfE2jRHUidgBBQWt
Retrigger CI after fixing the docker runner's node image label
Some checks failed
CI / frontend (pull_request) Failing after 2m35s
CI / backend (pull_request) Failing after 1s
8465a40aab
Retrigger CI after joining job containers to docker-net
Some checks failed
CI / frontend (pull_request) Failing after 30s
CI / backend (pull_request) Failing after 1s
aae64fdd77
Retrigger CI - confirmed config.yaml network=docker-net is loaded and runner restarted
Some checks failed
CI / frontend (pull_request) Failing after 35s
CI / backend (pull_request) Failing after 1s
9fa0fc8f4a
Retrigger CI - runner daemon now started with --config /data/config.yaml
Some checks failed
CI / frontend (pull_request) Failing after 22s
CI / backend (pull_request) Failing after 1s
1d53f0ce19
Bump CI/CD Node version to 22 (vitest 5 requires >=22.12)
Some checks failed
CI / frontend (pull_request) Successful in 27s
CI / backend (pull_request) Failing after 1s
e89716c6be
CI failed with "webidl.util.markAsUncloneable is not a function" -
vitest@5.0.0 requires Node ^22.12/^24/>=26, but node-version was pinned
to 20 in every setup-node step.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012rTfG1xfE2jRHUidgBBQWt
Replace dtolnay/rust-toolchain with a direct rustup install
All checks were successful
CI / frontend (pull_request) Successful in 25s
CI / backend (pull_request) Successful in 6m58s
bdcddd71e2
data.forgejo.org only mirrors a curated set of GitHub actions, and
dtolnay/rust-toolchain isn't one of them ("repository not found").
Install Rust directly via the official rustup script/rustup-init.exe
instead, so the workflow doesn't depend on third-party action mirroring.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012rTfG1xfE2jRHUidgBBQWt
Sign in to join this conversation.
No reviewers
No labels
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
Lemarkis/Mark-it!1
No description provided.