Track libneo release/26.2 and unify resolver#353
Conversation
bb55b1e to
8b14ff7
Compare
8b14ff7 to
57b2529
Compare
57b2529 to
457a8c6
Compare
457a8c6 to
e4dbd2a
Compare
e4dbd2a to
1621e61
Compare
Switch to tag 26.2.0 before merge. Explicit LIBNEO_BRANCH overrides still win.
1621e61 to
288c131
Compare
Adopt the canonical find_or_fetch shared across the codes: resolve libneo via LIBNEO_REF (cache or env, a branch/tag/commit validated against the remote and ignored if absent), then the committed LIBNEO_RELEASE (release/26.2), then the matching branch or main. Drop the legacy $CODE/SOURCE_DIR local-path shortcut; libneo is always fetched at the resolved ref.
|
@krystophny heads-up: this PR is part of a cross-repo change unifying how the codes resolve libneo (a validated |
# Conflicts: # cmake/Util.cmake
|
Superseded by the new release model (no release branches / versions): SIMPLE floats on libneo main and is validated per libneo PR via the reverse-dependency gate. The |
Risk tier
Correctness contract
Intended behavior change
Pin the default libneo fetch branch to the
release/26.2line for validation, unlessLIBNEO_BRANCHis supplied by CMake or the environment.Behavior that must not change
Explicit
LIBNEO_BRANCHoverrides still win. Before this PR merges, the default must be changed from the release branch to the released tag26.2.0.Coordinate / unit conventions
Unchanged.
Numerical invariants
Unchanged. This is a dependency pin only.
Tests added
Golden-record impact
Failure modes considered
mainor a moving branch on SIMPLEmain.Manual validation
The branch remains draft. It should not merge until
release/26.2is replaced by tag26.2.0.Verification