The path dependency on ../../bread-ecosystem/bread-theme (and bread-utils) assumed a sibling checkout that doesn't exist on the CI runner — this was the actual cause of release.yml never having succeeded, on top of the Tauri build-path issue fixed separately. Switched to a git dependency pinned to branch = "main" rather than a tag, since the functions this migration needs (css_custom_properties/css_tokens) aren't in a tagged bread-theme release yet. Verified with a full local build. |
||
|---|---|---|
| .forgejo/workflows | ||
| frontend | ||
| packaging | ||
| src | ||
| .gitignore | ||
| bakery.toml | ||
| LICENSE | ||
| README.md | ||
bos-settings
System settings app for BOS (Bread Operating System) — GTK4, configures every bread* app's config plus core system settings (network, sound, power, users, firewall, snapshots, packages, AUR, firmware, Hyprland display/appearance/autostart) non-destructively.
Split out of the bos repo into its own repo so a bos-settings release doesn't require a BOS ISO release, and vice versa. Distributed via bakery — see bread-ecosystem's CONTRIBUTING.md for the dev/beta/stable track workflow shared across the bread ecosystem.
Building
cargo build --release
Packaging / releasing
Bump Cargo.toml's version, tag vX.Y.Z, push the tag to both remotes — .forgejo/workflows/release.yml builds and publishes to dl.breadway.dev (bakery) automatically. Pushes to dev/beta publish a dev/beta-track build the same way, no tag needed.