This repo's CI currently references cpp-FuSa via unpinned (default branch) rather than an explicit version pin (same cpp-FuSa checkout pattern as cpp-CAN -- add ref: v0.15.0).
This is a reproducibility and stability risk: an upstream change to cpp-FuSa's default branch can silently change or break this repo's CI with no corresponding commit in this repo to explain why.
This is part of an ecosystem-wide policy decision to pin every x-Net repo (all languages) to an explicit, deliberately-upgraded cpp-FuSa version, matching what the Go x-Net repos already do (and are being updated to do consistently, see the parallel go-FuSa v0.36.0 pin-update pass).
Note that pinning to v0.15.0 (today's latest) may surface checks that were not being enforced before, since floating on main meant this repo was already exposed to whatever the newest checks are anyway -- so behavior should be similar, but flag that verification is still required.
This issue will be actioned directly as part of this pass, not left open.
This repo's CI currently references cpp-FuSa via unpinned (default branch) rather than an explicit version pin (same cpp-FuSa checkout pattern as cpp-CAN -- add
ref: v0.15.0).This is a reproducibility and stability risk: an upstream change to cpp-FuSa's default branch can silently change or break this repo's CI with no corresponding commit in this repo to explain why.
This is part of an ecosystem-wide policy decision to pin every x-Net repo (all languages) to an explicit, deliberately-upgraded cpp-FuSa version, matching what the Go x-Net repos already do (and are being updated to do consistently, see the parallel go-FuSa v0.36.0 pin-update pass).
Note that pinning to v0.15.0 (today's latest) may surface checks that were not being enforced before, since floating on main meant this repo was already exposed to whatever the newest checks are anyway -- so behavior should be similar, but flag that verification is still required.
This issue will be actioned directly as part of this pass, not left open.