Skip to content

Bump package versions to latest upstream releases - #59

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

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

Conversation

@github-actions

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 #59: Bump package versions to latest upstream releases

Head SHA: 2fceabd67138d503c1b3b4bc56b771d52a5e4eec (branch: bump-versions-20260915)
Base: origin/main (8ba166a51f3a0d7761d73f3e64d285f3c8ab256d)
Verdict: HOLD
Score: 5/10


Verification Summary

  1. 3-Way Merge Check:

    • Simulated 3-way merge against origin/main:
      git merge-tree --write-tree origin/main 2fceabd67138d503c1b3b4bc56b771d52a5e4eec
    • Exit code: 0 (clean merge). Resulting tree: b29a89813c730f307eb547db1f51834460e5bb6f.
  2. Diff Inspection (versions.env):

    • SERIALIZE_VERSION: 1.15.0 -> 1.17.0
    • RELIABLE_VERSION: 1.4.0 -> 1.4.5
    • NETCODE_VERSION: 1.4.3 -> 1.4.8
    • YOJIMBO_VERSION: 1.10.1 -> 1.13.5
    • SCHEMA_VERSION: 2.0.0 -> 2.5.0
  3. Release Script Verification:

    • Ran ./scripts/check-releases.sh in the worktree tracking 2fceabd67138d503c1b3b4bc56b771d52a5e4eec:
      all pinned versions are current
      
      Exited 0.
    • Negative Control / Red-Test:
      • Temporarily mutated versions.env to SERIALIZE_VERSION=1.15.0.
      • Executed ./scripts/check-releases.sh: correctly reported serialize: pinned 1.15.0, latest 1.17.0 and exited 1.
      • Restored worktree cleanly.
  4. CI Build Implications & Remote Failure Analysis:

    • Inspected workflow runs triggered on branch bump-versions-20260915 at commit 2fceabd67138d503c1b3b4bc56b771d52a5e4eec.
    • Workflow dispatch run 34953063512 (build.yml) failed across all 10 matrix build jobs (debian:12, debian:13, ubuntu:22.04, ubuntu:24.04, ubuntu:26.04 on both amd64 and arm64).
    • Detailed breakdown from the CI logs:
      • serialize 1.17.0: built, tested, and installed cleanly.
      • reliable 1.4.5: built, tested, and installed cleanly.
      • netcode 1.4.8: built, tested, and installed cleanly.
      • schema 2.5.0: built and passed autopkgtest-schema.
      • yojimbo 1.13.5: Failed in all 10 jobs during override_dh_auto_test:
        make[1]: Entering directory '/__w/apt/apt/build/yojimbo/yojimbo-1.13.5'
        /__w/apt/apt/build/yojimbo/yojimbo-1.13.5/bin/test
        make[1]: /__w/apt/apt/build/yojimbo/yojimbo-1.13.5/bin/test: No such file or directory
        make[1]: *** [debian/rules:20: override_dh_auto_test] Error 127
        
    • Root Cause:
      • In upstream mas-bandwidth/yojimbo v1.13.5 (PR #356 / YJ-06), test and example executables are now output to the CMake binary directory (CMAKE_BINARY_DIR/bin), rather than written into the source tree (CMAKE_CURRENT_SOURCE_DIR/bin). Upstream also added full CTest integration (enable_testing() and add_test(...)).
      • Both packages/yojimbo/debian/rules and official/yojimbo/debian/rules currently contain:
        override_dh_auto_test:
        ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
            $(CURDIR)/bin/test
        endif
      • Because $(CURDIR)/bin/test is absent, the debhelper build aborts with Error 127.
  5. Recommendation:

    • Place this PR on HOLD until packaging rules are updated to handle the new binary output location (or delegate testing to dh_auto_test via CTest). Merging in this state will break the main apt repository publishing workflow.

READ-COST: reader=Emma model=gemini-2.5-pro seconds=230 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