chore(ci): rename publish-binary.yml to build-linux.yml #20

Merged

David merged 1 commit from chore/rename-workflow-build-linux into main

2026-05-14 16:35:22 +02:00

David commented

2026-05-14 16:33:30 +02:00

Owner

Summary

Renames .forgejo/workflows/publish-binary.yml to build-linux.yml to match the workflow naming convention used by sibling repos in a8n-run/. Binary-publishing repos consistently use build-<artifact>.yml:

da-os/.forgejo/workflows/build-linux.yml and build-windows.yml (closest match: also Rust, also publishes to the Generic Package registry).
dmarc-reporter/.forgejo/workflows/build-backend.yml and build-frontend.yml.

The governance CHECKLIST.md only spells out build-oci-image.yml for image-publishing repos, so for a Generic-Package-only binary like yt the de facto convention from siblings is the right thing to mirror.

What changed

File: .forgejo/workflows/publish-binary.yml -> .forgejo/workflows/build-linux.yml.
Inside the workflow: name: Publish binary -> name: Build Linux binary; job id publish -> build-linux; job display name Build and publish yt binary -> Build yt (Linux x86_64); self-referential paths: filter follows.
CLAUDE.md workflow inventory updated.

No CI behavior changes: artifact filename (yt-linux-x86_64), Generic Package slug (youtrack-cli), registry URL, and other trigger paths are otherwise identical.

Verification

cargo fmt --check clean.
cargo clippy --all-targets -- -D warnings clean.
cargo test --all-targets: 160 tests pass.

Test plan

After merge, the next push that touches src/** or Cargo.toml triggers the renamed workflow and publishes yt-linux-x86_64 to the same URL as before.
Forgejo Actions UI shows the workflow listed as "Build Linux binary".

## Summary Renames `.forgejo/workflows/publish-binary.yml` to `build-linux.yml` to match the workflow naming convention used by sibling repos in `a8n-run/`. Binary-publishing repos consistently use `build-<artifact>.yml`: - `da-os/.forgejo/workflows/build-linux.yml` and `build-windows.yml` (closest match: also Rust, also publishes to the Generic Package registry). - `dmarc-reporter/.forgejo/workflows/build-backend.yml` and `build-frontend.yml`. The governance `CHECKLIST.md` only spells out `build-oci-image.yml` for image-publishing repos, so for a Generic-Package-only binary like `yt` the de facto convention from siblings is the right thing to mirror. ## What changed - File: `.forgejo/workflows/publish-binary.yml` -> `.forgejo/workflows/build-linux.yml`. - Inside the workflow: `name: Publish binary` -> `name: Build Linux binary`; job id `publish` -> `build-linux`; job display name `Build and publish yt binary` -> `Build yt (Linux x86_64)`; self-referential `paths:` filter follows. - `CLAUDE.md` workflow inventory updated. No CI behavior changes: artifact filename (`yt-linux-x86_64`), Generic Package slug (`youtrack-cli`), registry URL, and other trigger paths are otherwise identical. ## Verification - `cargo fmt --check` clean. - `cargo clippy --all-targets -- -D warnings` clean. - `cargo test --all-targets`: 160 tests pass. ## Test plan - [ ] After merge, the next push that touches `src/**` or `Cargo.toml` triggers the renamed workflow and publishes `yt-linux-x86_64` to the same URL as before. - [ ] Forgejo Actions UI shows the workflow listed as "Build Linux binary".

David added 1 commit

2026-05-14 16:33:30 +02:00

chore(ci): rename publish-binary.yml to build-linux.yml

Check / fmt + clippy + build + tests (pull_request) Successful in 8s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

8a970ca4b8

Matches the workflow naming convention used elsewhere in `a8n-run/`: binary-publishing repos use `build-<artifact>.yml` (see `da-os/.forgejo/workflows/build-linux.yml` and `build-windows.yml`, and `dmarc-reporter`'s `build-backend.yml` / `build-frontend.yml`). The governance CHECKLIST only spells out `build-oci-image.yml` for image-publishing repos; for a Generic-Package-only binary like `yt`, the de facto convention from siblings is what to mirror. Renames the file and updates the inside-file `name` (`Publish binary` -> `Build Linux binary`), the job id (`publish` -> `build-linux`), the job display name (`Build and publish yt binary` -> `Build yt (Linux x86_64)`), and the self-referential `paths:` filter. CLAUDE.md's workflow inventory is updated to match. No CI behavior changes; the artifact filename, package slug, registry URL, and trigger paths are otherwise identical. 160 tests still pass; clippy/fmt clean.