CI: drop GitHub and SSH dependencies from Forgejo workflows #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/forgejo-native"
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?
Replace actions-rust-cross/cross (GitHub-hosted actions, cross binary
from GitHub Releases, ghcr.io images run through the Docker socket,
which the runners do not expose) with cargo-zigbuild and a pinned,
checksummed zig toolchain. Replace Swatinem/rust-cache with the Forgejo
cache action and source all actions from data.forgejo.org. Use the
forgejo context and token instead of the github compatibility names.
Check out over HTTPS with actions/checkout in both workflows and push
the manuf update with the automatic token, so the SSH_PRIVATE_KEY
secret is no longer needed.
Point the libwifi submodule at a relative URL so it resolves to the
public mirror next to this repository on the same Forgejo instance.
Pin arm-unknown-linux-musleabi to Rust 1.95.0: newer releases emit
fminimum_num/fmaximum_num libcalls on soft-float ARMv6 that zig's
bundled musl does not provide.
Move the issue template to .forgejo/ and drop the GitHub-only
FUNDING.yml.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Pull request closed