Commit graph

4 commits

Author SHA1 Message Date
Breadway
7ab28d30a7 Fix review-queue dead ends and harden grab/import/API paths
Some checks failed
check / check (push) Failing after 14m5s
dev release / build (push) Successful in 3m54s
Stop upgrade-search from queuing mid-confidence matches that approve
cannot honor (owned movies/episodes 409'd on the TUI). De-dupe pending
review rows, scope 1080p gates to the target episode, refuse unsafe
pack cleanup, and require a token for non-loopback binds.
2026-08-16 00:44:58 +08:00
Breadway
3cbac5ffe9 CI: onboard breadarr onto the bakery distribution system
Adds bakery.toml (system_deps verified via ldd + Command::new grep against
breadarrd/src, not guessed) and dev-release.yml/rc-release.yml/release.yml
following bread-ecosystem's current single-trunk + RC-tag CI model. No
GitHub Release step anywhere — this repo has no GitHub mirror.
2026-08-05 19:04:22 +08:00
Breadway
2e32488b26 Remove orphaned bakery.toml — nothing serves it
breadarr has no .forgejo/workflows at all (no mirror, release, or
package workflow) and no PKGBUILD, and it isn't listed in
bread-ecosystem's registry/bread-ecosystem.toml, so gen-index.sh would
never pick it up even if a release workflow existed. The bakery.toml
here was pure dead metadata.

Not wiring up a release workflow instead: breadarr isn't in the
registry and its distribution channel (bakery, pacman, both, neither)
hasn't actually been decided, so adding one here would be inventing
a channel commitment I have no signal for. If/when breadarr is ready
to ship, follow docs/release-channels.md in bread-ecosystem to add it
properly (bakery.toml + registry entry + release.yml, or a PKGBUILD +
package.yml, or both).
2026-07-17 14:02:59 +08:00
Breadway
697b009627 can't be bothered writing a commit message 2026-07-16 22:22:53 +08:00