Bump package versions to latest upstream releases

[github-actions]

Automated bump from check-releases.yml. Merging rebuilds and republishes the apt repository.

[gafferongames]

Code Review: PR #46 (Bump package versions to latest upstream releases)

Head SHA: 9f960cd4d96503d981422884c8f51f24ccabc911
Base: origin/main (8ba166a51f3a0d7761d73f3e64d285f3c8ab256d)
Score: 7/10
Verdict: HOLD (Superseded by newer upstream releases and subsequent daily bump PRs, e.g. PR #65)

---

Summary & Diff Inspection

PR #46 updates four package pins in versions.env:

• RELIABLE_VERSION: 1.4.0 -> 1.4.1
• NETCODE_VERSION: 1.4.3 -> 1.4.4
• YOJIMBO_VERSION: 1.10.1 -> 1.11.0
• SCHEMA_VERSION: 2.0.0 -> 2.4.0
• SERIALIZE_VERSION: remains 1.15.0

Verification Evidence

1. 3-Way Merge Evaluation:

   • Executed: git merge-tree --write-tree origin/main 9f960cd4d96503d981422884c8f51f24ccabc911
   • Result: Exited 0, produced merge tree 51227352c658618e52a4f75ec8f43eba11c746c2.
   • Fast-forwards cleanly from origin/main without conflicts.

2. Upstream Source Tarball Verification:
   All 5 pinned upstream release archives were verified to exist and returned HTTP 200:

   • mas-bandwidth/serialize v1.15.0: HTTP 200
   • mas-bandwidth/reliable v1.4.1: HTTP 200
   • mas-bandwidth/netcode v1.4.4: HTTP 200
   • mas-bandwidth/yojimbo v1.11.0: HTTP 200
   • mas-bandwidth/schema v2.4.0: HTTP 200

3. Release Sensitivity & Script Verification (./scripts/check-releases.sh):

   • Running ./scripts/check-releases.sh against commit 9f960cd4d96503d981422884c8f51f24ccabc911 detects that upstream releases have progressed significantly since PR creation on 2026-09-02:
     • serialize: pinned 1.15.0, latest 1.17.0
     • reliable: pinned 1.4.1, latest 1.4.5
     • netcode: pinned 1.4.4, latest 1.4.8
     • yojimbo: pinned 1.11.0, latest 1.13.5
     • schema: pinned 2.4.0, latest 2.5.0
       Script exited 1 as expected when versions are stale.

4. Negative Controls / Red-Test:

   • Green Control: Updating versions.env to current upstream versions and running ./scripts/check-releases.sh produced all pinned versions are current and exit code 0.
   • Red Test: Introducing a single artificial version mismatch (RELIABLE_VERSION=0.0.1) caused ./scripts/check-releases.sh to isolate that exact discrepancy (reliable: pinned 0.0.1, latest 1.4.5) and exit code 1.

5. CI Build Implications & Remote CI Results:

   • In GitHub Actions workflow dispatch run 33614387613 on branch bump-versions-20260902:
     • All 10 platform matrix container builds succeeded across Debian 12/13 and Ubuntu 22.04/24.04/26.04 for both amd64 and arm64.
     • The autopkgtest-schema suite completed cleanly in 49s on Debian 13.
     • The sole failing step was publish, which failed as expected because branch bump-versions-20260902 is blocked by GitHub Pages environment protection rules (deployments restricted to main).

Verdict & Recommendation

Technically, the artifacts and packages in commit 9f960cd4d96503d981422884c8f51f24ccabc911 build and validate cleanly. However, because this PR is now 19 days old, upstream releases have advanced across all 5 repositories. Subsequent daily bump PRs (up to PR #65) have superseded this PR.

Recommendation: HOLD / Close PR #46 without merging in favor of evaluating the newest bump PR (#65).

READ-COST: reader=Emma model=gemini-2.5-pro seconds=179 tokens=unknown plan=max