Move CI to Forgejo Actions and add a release workflow #4

Merged

selu merged 5 commits from forgejo-release into master 2026-10-28 20:41:21 +00:00

Conversation 0 Commits 5 Files changed 5 +421 -72

selu commented 2026-10-28 18:39:06 +00:00

Owner

• Copy link
• Copy Markdown

Summary

• Move CI from .github/workflows/rust_ci.yml to .forgejo/workflows/ci.yml so it runs on Forgejo Actions.
• Add .forgejo/workflows/release.yml. On a v* tag push, it builds the firmware (ELF and a merged image) and static irbt binaries for Linux x86_64/aarch64 and Windows, then publishes a release with SHA256SUMS. It fails if the tag doesn't match the crate versions. You can also run it by hand to rebuild an existing tag.
• README: add a Releases section on the downloads, flashing, and cutting a release.
• Add docs/forgejo-runner.md on setting up a Forgejo runner.

Test plan

• CI workflow runs on this PR
• Push a prerelease tag (e.g. v0.2.1-rc1) and check the release assets

🤖 Generated with Claude Code

## Summary - Move CI from `.github/workflows/rust_ci.yml` to `.forgejo/workflows/ci.yml` so it runs on Forgejo Actions. - Add `.forgejo/workflows/release.yml`. On a `v*` tag push, it builds the firmware (ELF and a merged image) and static `irbt` binaries for Linux x86_64/aarch64 and Windows, then publishes a release with `SHA256SUMS`. It fails if the tag doesn't match the crate versions. You can also run it by hand to rebuild an existing tag. - README: add a Releases section on the downloads, flashing, and cutting a release. - Add `docs/forgejo-runner.md` on setting up a Forgejo runner. ## Test plan - [ ] CI workflow runs on this PR - [ ] Push a prerelease tag (e.g. `v0.2.1-rc1`) and check the release assets 🤖 Generated with [Claude Code](https://claude.com/claude-code)

selu added 1 commit 2026-10-28 18:39:06 +00:00

Move CI to Forgejo Actions and add a release workflow ... c458603164

Port the GitHub CI workflow to .forgejo/workflows/ci.yml and add
release.yml, which builds firmware and irbt binaries and publishes a
release when a v* tag is pushed. Document releases in the README and
runner setup in docs/forgejo-runner.md.

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

selu added 1 commit 2026-10-28 18:52:09 +00:00

Hide Forgejo's job token from espup ... 98158328ee

Forgejo sets GITHUB_TOKEN to its own job token. espup sends it to the
GitHub API, which rejects it, so the Xtensa toolchain install failed.
Clear it for the toolchain step so espup queries GitHub anonymously.

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

selu added 1 commit 2026-10-28 18:55:39 +00:00

Install the Xtensa toolchain without Forgejo's job token ... e2353e6636

Setting GITHUB_TOKEN to an empty value on the xtensa-toolchain step
didn't help: the runner overrides it inside the action. Replace the
action with a script that does the same thing after unsetting the
variable, with espup and ldproxy pinned.

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

selu added 1 commit 2026-10-28 19:55:01 +00:00

Cache the Xtensa toolchain in CI ... b14d42656f

Pin the Xtensa Rust toolchain to 1.99.0.0 and cache the esp toolchain
directory, which holds Rust, LLVM and GCC, so jobs skip espup install
on a cache hit. With the version pinned, espup no longer queries the
GitHub API.

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

selu added 1 commit 2026-10-28 20:16:26 +00:00

Pin the Xtensa toolchain to 1.97.0.0 ... 61412b3999

1.99.0.0 is a prerelease, and its std doesn't build for espidf
(libc::AT_FDCWD is missing). 1.97.0.0 is the latest release, the one
espup installed before the version was pinned.

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

selu merged commit 7199605dc0 into master 2026-10-28 20:41:21 +00:00

selu referenced this pull request from a commit 2026-10-28 20:41:22 +00:00

Merge pull request 'Move CI to Forgejo Actions and add a release workflow' (#4) from forgejo-release into master

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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

selu/ir-bt-bridge!4

No description provided.