Skip to content

Bump package versions to latest upstream releases - #50

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
bump-versions-20260906
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
bump-versions-20260906

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

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

@gafferongames

Copy link
Copy Markdown
Contributor

Review of PR #50: Bump package versions to latest upstream releases

  • Head SHA: 148a246b54ba49afb38e5c8ac228d2f16e55e2f5
  • Branch: bump-versions-20260906
  • Base: origin/main
  • Verdict: HOLD / CHANGES REQUESTED
  • Score: 2 / 10

Executive Summary

PR #50 is an automated version bump from check-releases.yml opened on 2026-09-06. While the git 3-way merge is completely clean without conflicts, the PR cannot be merged as-is:

  1. 100% CI Failure: Remote CI run 34024562637 failed across all 10 matrix legs (Debian 12/13, Ubuntu 22.04/24.04/26.04 on amd64 and arm64).
  2. Packaging Incompatibility: Upstream Yojimbo (since YJ-06) changed its CMake output directory from <source>/bin to ${CMAKE_BINARY_DIR}/bin. packages/yojimbo/debian/rules hardcodes $(CURDIR)/bin/test, which fails with Error 127 (No such file or directory) during out-of-source dh builds.
  3. Stale Pinned Versions: Because this PR was opened ~15 days ago, upstream releases have already advanced past all 5 pinned versions.

Verification Evidence

1. 3-Way Merge Simulation

git merge-tree --write-tree origin/main 148a246b54ba49afb38e5c8ac228d2f16e55e2f5
  • Merge Tree SHA: 5a5522236b723aa2cc27c8b11cdc2234271e9ff7
  • Exit Code: 0
  • Status: Clean merge, no git merge conflicts with origin/main.

2. Diff Inspection (versions.env)

--- a/versions.env
+++ b/versions.env
-SERIALIZE_VERSION=1.15.0
-RELIABLE_VERSION=1.4.0
-NETCODE_VERSION=1.4.3
-YOJIMBO_VERSION=1.10.1
-SCHEMA_VERSION=2.0.0
+SERIALIZE_VERSION=1.16.0
+RELIABLE_VERSION=1.4.2
+NETCODE_VERSION=1.4.5
+YOJIMBO_VERSION=1.12.1
+SCHEMA_VERSION=2.4.0

3. Upstream Version Check (./scripts/check-releases.sh)

Ran inside isolated worktree tracking 148a246b54ba49afb38e5c8ac228d2f16e55e2f5:

serialize: pinned 1.16.0, latest 1.17.0
reliable: pinned 1.4.2, latest 1.4.5
netcode: pinned 1.4.5, latest 1.4.8
yojimbo: pinned 1.12.1, latest 1.13.5
schema: pinned 2.4.0, latest 2.5.0
  • Exit Code: 1 (all 5 packages are behind current latest releases).

4. Negative Control / Red-Test Verification

Sensitivity of ./scripts/check-releases.sh was experimentally validated in the isolated worktree:

  • Green Control: Running ./scripts/check-releases.sh --update followed by ./scripts/check-releases.sh returned:
    all pinned versions are current
    
    with exit code 0.
  • Red Control (Negative Control): Mutating SERIALIZE_VERSION=0.99.0 in versions.env resulted in:
    serialize: pinned 0.99.0, latest 1.17.0
    
    with exit code 1.
    The check script is sensitive and properly detects mismatches.

5. Remote CI Analysis & Root Cause Diagnosis

Inspected GitHub Actions workflow dispatch run 34024562637 on branch bump-versions-20260906:

  • autopkgtest-schema: Succeeded (schema compiler v2.4.0 passed CLI test).
  • All 10 build legs failed with exit code 2:
    • Ubuntu 22.04 (amd64, arm64)
    • Ubuntu 24.04 (amd64, arm64)
    • Ubuntu 26.04 (amd64, arm64)
    • Debian 12 (amd64, arm64)
    • Debian 13 (amd64, arm64)
  • Failure Log Snippet (from build (debian:12, amd64)):
    [100%] Linking CXX executable bin/test
    make[3]: Leaving directory '/__w/apt/apt/build/yojimbo/yojimbo-1.12.1/obj-x86_64-linux-gnu'
       debian/rules override_dh_auto_test
    make[1]: Entering directory '/__w/apt/apt/build/yojimbo/yojimbo-1.12.1'
    make[1]: /__w/apt/apt/build/yojimbo/yojimbo-1.12.1/bin/test: No such file or directory
    make[1]: *** [debian/rules:20: override_dh_auto_test] Error 127
    make[1]: Leaving directory '/__w/apt/apt/build/yojimbo/yojimbo-1.12.1'
    make: *** [debian/rules:7: binary] Error 2
    dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
    
  • Root Cause:
    Upstream Yojimbo set:
    set(CMAKE_RUNTIME_OUTPUT_DIRECTORY "${CMAKE_BINARY_DIR}/bin")
    and added CTest entries (add_test).
    packages/yojimbo/debian/rules lines 18-21:
    override_dh_auto_test:
    ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
    	$(CURDIR)/bin/test
    endif
    Because dh performs out-of-source builds in obj-<gnu-triplet>, the executable was output to obj-<gnu-triplet>/bin/test. Looking for $(CURDIR)/bin/test fails with ENOENT.

Required Action Items

  1. Fix packages/yojimbo/debian/rules:
    Update override_dh_auto_test to run dh_auto_test (now supported via CTest in Yojimbo >= 1.12) or execute from the build directory:
    override_dh_auto_test:
    ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
    	dh_auto_test
    endif
  2. Refresh Versions:
    Either re-run scripts/check-releases.sh --update to advance to the latest upstream versions (serialize 1.17.0, reliable 1.4.5, netcode 1.4.8, yojimbo 1.13.5, schema 2.5.0), or close this PR and trigger a fresh bump once the packaging fix has landed on main.

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

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant