Context
Issue #15715 identified that master accumulates orphaned recipe files when master-next → master merges occur. Git treats recipe version bumps (file renames) as delete + add, so merging two branches that independently upgraded the same recipe results in both versions being kept silently.
Proposal
Add a CI check (pre-merge hook or workflow) that runs on release merge PRs (master-next → master) to detect when multiple .bb files exist for the same recipe name (e.g., python3-botocore_1.42.93.bb AND python3-botocore_1.43.6.bb).
The check should:
- Scan for duplicate recipe names with different versions in the merge result
- Fail the merge if duplicates are found
- Suggest which files to delete (keep only the highest version)
Priority
Post-release. The immediate cleanup of stale files on master can be done as a one-time commit (see #15715).
Context
Issue #15715 identified that master accumulates orphaned recipe files when master-next → master merges occur. Git treats recipe version bumps (file renames) as delete + add, so merging two branches that independently upgraded the same recipe results in both versions being kept silently.
Proposal
Add a CI check (pre-merge hook or workflow) that runs on release merge PRs (master-next → master) to detect when multiple
.bbfiles exist for the same recipe name (e.g.,python3-botocore_1.42.93.bbANDpython3-botocore_1.43.6.bb).The check should:
Priority
Post-release. The immediate cleanup of stale files on master can be done as a one-time commit (see #15715).