Skip to content

Bump package versions to latest upstream releases - #54

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

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

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

  • Head SHA: 485f51670bc8c43fca8fa7a2082a045fd456340c
  • Base SHA: origin/main (8ba166a51f3a0d7761d73f3e64d285f3c8ab256d)
  • Score: 3/10
  • Verdict: HOLD

Verification Summary

1. 3-Way Merge Check

  • Ran git merge-tree --write-tree origin/main 485f51670bc8c43fca8fa7a2082a045fd456340c.
  • Exit code: 0
  • Merge tree: c4bbd7dd950d112a827b96e39ab114aed1594c49
  • Git merge is clean with no merge conflicts against origin/main.

2. Diff Inspection (versions.env)

The commit bumps five packages:

  • SERIALIZE_VERSION: 1.15.0 -> 1.17.0
  • RELIABLE_VERSION: 1.4.0 -> 1.4.2
  • NETCODE_VERSION: 1.4.3 -> 1.4.5
  • YOJIMBO_VERSION: 1.10.1 -> 1.13.0
  • SCHEMA_VERSION: 2.0.0 -> 2.5.0

3. Release Staleness Check (./scripts/check-releases.sh)

  • Ran ./scripts/check-releases.sh in isolated scratch worktree tracking 485f51670bc8c43fca8fa7a2082a045fd456340c.
  • Result: Exit code 1 (stale).
  • Findings:
    • reliable: pinned 1.4.2, latest 1.4.5
    • netcode: pinned 1.4.5, latest 1.4.8
    • yojimbo: pinned 1.13.0, latest 1.13.5
    • (serialize 1.17.0 and schema 2.5.0 are current)
  • The PR was opened on 2026-09-10 and newer upstream releases have shipped since.

4. Remote CI Results & Build Implications

  • Inspected remote GitHub Actions run 34460842065 (dispatched on branch bump-versions-20260910).
  • Result: Failed (all 10 matrix builds across Debian 12/13 and Ubuntu 22.04/24.04/26.04 on amd64 and arm64 failed with exit code 2).
  • Root Cause:
    packages/yojimbo/debian/rules contains:
override_dh_auto_test:
ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
	$(CURDIR)/bin/test
endif

In CI build log:
make[1]: /__w/apt/apt/build/yojimbo/yojimbo-1.13.0/bin/test: No such file or directory
make[1]: *** [debian/rules:20: override_dh_auto_test] Error 127

  • Upstream Yojimbo 1.13.0 changed its CMake layout (change YJ-06): executables are placed in ${CMAKE_BINARY_DIR}/bin rather than the source root, and standard CTest registration was added (enable_testing(), add_test(NAME yojimbo_test COMMAND yojimbo_test)).
  • Consequently, Yojimbo fails to build in the packaging pipeline without updating packages/yojimbo/debian/rules.

5. Negative Controls / Sensitivity Verification

  • Negative Control 1 (Sensitivity to version mismatch): Mutated SERIALIZE_VERSION=0.0.1 in versions.env. Script correctly flagged serialize: pinned 0.0.1, latest 1.17.0 and exited with status 1.
  • Negative Control 2 (Clean pass on up-to-date releases): Tested with ./scripts/check-releases.sh --update, then reran ./scripts/check-releases.sh. Script reported all pinned versions are current and exited with status 0.
  • Restored worktree to pristine HEAD state at 485f51670bc8c43fca8fa7a2082a045fd456340c.

Conclusion & Required Actions

Verdict: HOLD

  1. Update packages/yojimbo/debian/rules to accommodate Yojimbo 1.13.0+'s build output directory and CTest integration.
  2. Re-run ./scripts/check-releases.sh --update to capture the latest releases (reliable 1.4.5, netcode 1.4.8, yojimbo 1.13.5) once the packaging rules are fixed.

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