fix(ci): repair Forgejo workflows after the axum rewrite

nrupard commented

2026-05-04 16:50:49 +02:00

Owner

Both Forgejo workflows kept references to paths and tooling that no longer existed after the rewrite from Dioxus to Axum + Askama, so they either never triggered or would have failed if they had.

build-oci-image.yml now watches the rewritten paths under server/ (server/src, server/migrations, server/templates, server/assets, server/package.json, server/bun.lock, server/tailwind.config.js) instead of the obsolete top-level src/, migrations/, assets/, and .cargo/. Cargo.toml/Cargo.lock and the Dockerfile/get-tags.nu are still watched. The Dockerfile itself was already up to date and is unchanged.

build-desktop-linux.yml referenced ci-build/Dockerfile.desktop-linux and a Dioxus output path (target/dx/lets-chat/release/linux/app/lets-chat) that were both removed when the rewrite landed, so the desktop CI build had no chance of succeeding. This commit:

Reintroduces ci-build/Dockerfile.desktop-linux as a single-stage rust:1.88-slim-bookworm image that installs the GTK / WebKit2GTK / Soup native deps and runs cargo build --release -p lets-chat-desktop. The artifact is the plain ELF binary at /build/target/release/lets-chat-desktop, which docker cp extracts in the next step.
Updates the workflow's path filters to desktop/src, desktop/Cargo.toml, server/src (the desktop crate links the server lib for shared models), Cargo.toml, Cargo.lock, and the new Dockerfile + get-tags.nu.
Updates the artifact extraction path and the uploaded artifact name to reflect the new binary name (lets-chat-desktop).

Locally verified that ci-build/Dockerfile.desktop-linux builds and that docker cp pulls a valid x86-64 ELF binary from /build/target/release/lets-chat-desktop.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

Both Forgejo workflows kept references to paths and tooling that no longer existed after the rewrite from Dioxus to Axum + Askama, so they either never triggered or would have failed if they had. build-oci-image.yml now watches the rewritten paths under server/ (server/src, server/migrations, server/templates, server/assets, server/package.json, server/bun.lock, server/tailwind.config.js) instead of the obsolete top-level src/, migrations/, assets/, and .cargo/. Cargo.toml/Cargo.lock and the Dockerfile/get-tags.nu are still watched. The Dockerfile itself was already up to date and is unchanged. build-desktop-linux.yml referenced ci-build/Dockerfile.desktop-linux and a Dioxus output path (target/dx/lets-chat/release/linux/app/lets-chat) that were both removed when the rewrite landed, so the desktop CI build had no chance of succeeding. This commit: - Reintroduces ci-build/Dockerfile.desktop-linux as a single-stage rust:1.88-slim-bookworm image that installs the GTK / WebKit2GTK / Soup native deps and runs cargo build --release -p lets-chat-desktop. The artifact is the plain ELF binary at /build/target/release/lets-chat-desktop, which docker cp extracts in the next step. - Updates the workflow's path filters to desktop/src, desktop/Cargo.toml, server/src (the desktop crate links the server lib for shared models), Cargo.toml, Cargo.lock, and the new Dockerfile + get-tags.nu. - Updates the artifact extraction path and the uploaded artifact name to reflect the new binary name (lets-chat-desktop). Locally verified that ci-build/Dockerfile.desktop-linux builds and that docker cp pulls a valid x86-64 ELF binary from /build/target/release/lets-chat-desktop. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

nrupard added 1 commit

2026-05-04 16:50:49 +02:00

fix(ci): repair Forgejo workflows after the axum rewrite f5a83d7be9

Both Forgejo workflows kept references to paths and tooling that no longer existed after the rewrite from Dioxus to Axum + Askama, so they either never triggered or would have failed if they had.

build-oci-image.yml now watches the rewritten paths under server/ (server/src, server/migrations, server/templates, server/assets, server/package.json, server/bun.lock, server/tailwind.config.js) instead of the obsolete top-level src/, migrations/, assets/, and .cargo/. Cargo.toml/Cargo.lock and the Dockerfile/get-tags.nu are still watched. The Dockerfile itself was already up to date and is unchanged.

build-desktop-linux.yml referenced ci-build/Dockerfile.desktop-linux and a Dioxus output path (target/dx/lets-chat/release/linux/app/lets-chat) that were both removed when the rewrite landed, so the desktop CI build had no chance of succeeding. This commit:

- Reintroduces ci-build/Dockerfile.desktop-linux as a single-stage rust:1.88-slim-bookworm image that installs the GTK / WebKit2GTK / Soup native deps and runs cargo build --release -p lets-chat-desktop. The artifact is the plain ELF binary at /build/target/release/lets-chat-desktop, which docker cp extracts in the next step.
- Updates the workflow's path filters to desktop/src, desktop/Cargo.toml, server/src (the desktop crate links the server lib for shared models), Cargo.toml, Cargo.lock, and the new Dockerfile + get-tags.nu.
- Updates the artifact extraction path and the uploaded artifact name to reflect the new binary name (lets-chat-desktop).

Locally verified that ci-build/Dockerfile.desktop-linux builds and that docker cp pulls a valid x86-64 ELF binary from /build/target/release/lets-chat-desktop.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

nrupard merged commit 62b8760c56 into main

2026-05-04 16:50:56 +02:00

nrupard deleted branch fix/forgejo-workflows

2026-05-04 16:50:56 +02:00

nrupard referenced this pull request from a commit

2026-05-04 16:50:57 +02:00

Merge pull request 'fix(ci): repair Forgejo workflows after the axum rewrite' (#28) from fix/forgejo-workflows into main

Rows
Columns

fix(ci): repair Forgejo workflows after the axum rewrite #28