ci: build dev track and PR checks against dependency main #7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/dev-deps-main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of ECO-38.
check.yml and dev-release.yml now clone bread-ecosystem's main once, run scripts/lint-pins.sh (check.yml only) and scripts/dev-deps.sh to patch bread-theme and bread-utils (both from bread-ecosystem) to their own main branch, and build without --locked. Cargo.toml stays tag-pinned throughout; nothing is committed back.
release.yml and beta-release.yml are untouched (per CONTRIBUTING.md, beta-release.yml is a known leftover from the old three-branch model and is deliberately not being rewritten here).
DEV_DEPS_DIR is left at its default (a true sibling of the checkout): breadcast is a Cargo workspace, so forcing the clone inside the checkout breaks Cargo's workspace-field inheritance. ci/bread-ecosystem.rev is bumped to pick up bread-ecosystem's ci/build.sh fix for this.
Also fixes the dev index regeneration step, which was still cloning bread-ecosystem's
devbranch (removed in bread-ecosystem's single-trunk migration; checked breadcast's CI history and every single dev-release run has been failing outright because of this), reusing the same bread-ecosystem clone dev-deps.sh uses instead of a second, separate one that was pointed at a branch that no longer exists.Verified locally end to end: lint-pins, dev-deps.sh with its default sibling DEV_DEPS_DIR, and a dockerized cargo clippy --workspace through ci/build.sh all pass against a real breadcast checkout. Cargo.lock verified fresh and every git.breadway.dev dependency is already tag-pinned.