Rebuilds fleet-protocol-cpp v1.2.0 against fleet-protocol-interface v2.1.0 on all four target platforms (fleet-os-3, ubuntu24.04, fedora44, debian12), via build-package --build-deps (keep-everything), so each chain dep (aeron, async-function-execution, fleet-protocol-interface, zlib, protobuf) is rebuilt and committed alongside.
These are the direct fpi downstreams and are consistent with fpi v2.1.0.
Not included (separate follow-up): the apps (io-module, mission-module, module-gateway, transparent-module) and fleet-protocol-internal-client cannot be rebuilt from their currently-pinned context tags — those tags predate the dep bumps (e.g. io-module v1.3.4 wants nlohmann-json v3.10.5; mission-module v1.3.2 wants fpi v2.0.0). They need new release tags pinning current deps before they can be rebuilt. teleop-module additionally needs GitLab credentials in the build container.
Rebuilds **fleet-protocol-cpp v1.2.0** against **fleet-protocol-interface v2.1.0** on all four target platforms (fleet-os-3, ubuntu24.04, fedora44, debian12), via `build-package --build-deps` (keep-everything), so each chain dep (aeron, async-function-execution, fleet-protocol-interface, zlib, protobuf) is rebuilt and committed alongside.
These are the **direct fpi downstreams** and are consistent with fpi v2.1.0.
**Not included** (separate follow-up): the apps (io-module, mission-module, module-gateway, transparent-module) and fleet-protocol-internal-client cannot be rebuilt from their currently-pinned context tags — those tags predate the dep bumps (e.g. io-module v1.3.4 wants nlohmann-json v3.10.5; mission-module v1.3.2 wants fpi v2.0.0). They need new release tags pinning current deps before they can be rebuilt. teleop-module additionally needs GitLab credentials in the build container.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Rebuilds fleet-protocol-cpp v1.2.0 against fleet-protocol-interface v2.1.0 on all four target platforms (fleet-os-3, ubuntu24.04, fedora44, debian12), via
build-package --build-deps(keep-everything), so each chain dep (aeron, async-function-execution, fleet-protocol-interface, zlib, protobuf) is rebuilt and committed alongside.These are the direct fpi downstreams and are consistent with fpi v2.1.0.
Not included (separate follow-up): the apps (io-module, mission-module, module-gateway, transparent-module) and fleet-protocol-internal-client cannot be rebuilt from their currently-pinned context tags — those tags predate the dep bumps (e.g. io-module v1.3.4 wants nlohmann-json v3.10.5; mission-module v1.3.2 wants fpi v2.0.0). They need new release tags pinning current deps before they can be rebuilt. teleop-module additionally needs GitLab credentials in the build container.