[BUG] Main CI can hide incompatible providers behind feature branches #778

Open
opened 2026-11-12 19:11:46 +01:00 by erikinkinen · 1 comment
Owner

Summary

Main and release CI can resolve a configured feature supplier instead of its
actual main branch, masking incompatibility between the repositories' main
versions.

Reproduction

Use a valid companion profile whose provider has different main and feature
commits. Resolve it for a main-branch or tag job. The existing resolver chooses
the configured feature ref regardless of the CI ref.

Expected and actual behavior

Main and tag jobs must qualify actual main providers. Feature jobs may select
explicit companions. Previously both used the feature mapping, allowing an older
provider contract to stand in for current main.

Environment and identity

  • Integration shared helper: 438667a219737bd50d3b5302e0709ae40ab80ce8.
  • Route: central companion profile, original bounded Git queries and immutable
    per-run source snapshots. No VM or additional authority is needed.
  • Example boundary: the earlier bootloader handoff stage and current lib-handoff
    main use different versions; qualifying the earlier stage is a separate job.

Evidence and prior checks

The feature includes a genuine Git fixture with distinct main and feature
commits. It checks the actual selected ref and commit, refusal of feature
snapshots in main mode, and refusal before source reads when main CI requests a
feature-policy override.

Tracking

Keep feature-stage qualification separate from main and release qualification.

## Summary Main and release CI can resolve a configured feature supplier instead of its actual main branch, masking incompatibility between the repositories' main versions. ## Reproduction Use a valid companion profile whose provider has different main and feature commits. Resolve it for a main-branch or tag job. The existing resolver chooses the configured feature ref regardless of the CI ref. ## Expected and actual behavior Main and tag jobs must qualify actual main providers. Feature jobs may select explicit companions. Previously both used the feature mapping, allowing an older provider contract to stand in for current main. ## Environment and identity - Integration shared helper: `438667a219737bd50d3b5302e0709ae40ab80ce8`. - Route: central companion profile, original bounded Git queries and immutable per-run source snapshots. No VM or additional authority is needed. - Example boundary: the earlier bootloader handoff stage and current lib-handoff main use different versions; qualifying the earlier stage is a separate job. ## Evidence and prior checks The feature includes a genuine Git fixture with distinct main and feature commits. It checks the actual selected ref and commit, refusal of feature snapshots in main mode, and refusal before source reads when main CI requests a feature-policy override. ## Tracking Keep feature-stage qualification separate from main and release qualification.
erikinkinen added this to the Alpha 1 milestone 2026-11-12 19:11:46 +01:00
Author
Owner

Implemented in #779 and integrated into the shared development helper at af3e62821a5bb0e54d0a0cbf73c6ef73686e8e9a. Main and tag jobs now select actual main providers; feature jobs retain explicit companions. Main-mode replay refuses feature snapshots.

The code change is a5077762. The frontend and consumer source boundaries are documented separately. This has not been merged into main.

Implemented in [#779](https://git.erikinkinen.fi/erix/integration/pulls/779) and integrated into the shared development helper at `af3e62821a5bb0e54d0a0cbf73c6ef73686e8e9a`. Main and tag jobs now select actual main providers; feature jobs retain explicit companions. Main-mode replay refuses feature snapshots. The code change is [a5077762](https://git.erikinkinen.fi/erix/integration/commit/a50777629d33e1ee7bea94ebcfdbf7ce36d9daa6). The [frontend and consumer source boundaries](https://git.erikinkinen.fi/erix/integration/src/commit/af3e62821a5bb0e54d0a0cbf73c6ef73686e8e9a/docs/development-dependencies.md) are documented separately. This has not been merged into main.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#778
No description provided.