Skip to content

Bump package versions to latest upstream releases - #43

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

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

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

Child Review: PR #43 (mas-bandwidth/apt)

  • Commit Head SHA: 6c4a15d0565d21fc294a287d53c002841f5c556d
  • Branch: bump-versions-20260830
  • Base: origin/main (8ba166a51f3a0d7761d73f3e64d285f3c8ab256d)
  • Verdict: APPROVE (with advisory note on upstream releases)
  • Score: 8/10

1. Verification of 3-Way Merge

Tested 3-way merge against origin/main:

git merge-tree --write-tree origin/main 6c4a15d0565d21fc294a287d53c002841f5c556d
  • Result: Exit code 0
  • Tree SHA: 8e339985f4877961abfae1851bab09950a6f1514
  • Clean merge against base with zero conflicts.

2. Diff Inspection against Base (versions.env)

The commit modifies 3 lines in versions.env:

-RELIABLE_VERSION=1.4.0
-NETCODE_VERSION=1.4.3
-YOJIMBO_VERSION=1.10.1
+RELIABLE_VERSION=1.4.1
+NETCODE_VERSION=1.4.4
+YOJIMBO_VERSION=1.11.0

SERIALIZE_VERSION (1.15.0) and SCHEMA_VERSION (2.0.0) remain unchanged. The changes conform strictly to the expected environment format.


3. Check-Releases Script Execution

Ran ./scripts/check-releases.sh:

  • At PR generation time (2026-08-30), these bumped versions represented the latest upstream releases.
  • Evaluating against current GitHub releases (as of 2026-09-21) reports:
    • 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.0.0, latest 2.5.0
    • Exit code: 1 (stale).
  • Advisory Note: Upstream projects have shipped further minor/patch releases since this PR was opened 22 days ago. Merging this PR will successfully build and publish these intermediate versions, after which the daily check-releases.yml cron will automatically open a follow-up bump for current releases (or the maintainer can run ./scripts/check-releases.sh --update).

4. Remote CI Build Verification

Inspected GitHub Actions workflow run 33303992703 (event: workflow_dispatch, head SHA 6c4a15d0565d21fc294a287d53c002841f5c556d):

  • Package Matrix Builds: 10/10 jobs succeeded:
    • ubuntu:26.04 (amd64, arm64)
    • ubuntu:24.04 (amd64, arm64)
    • ubuntu:22.04 (amd64, arm64)
    • debian:13 (amd64, arm64)
    • debian:12 (amd64, arm64)
  • Schema Autopkgtest: autopkgtest-schema passed cleanly in 46s.
  • Artifacts: All 10 .deb distribution bundles generated and uploaded without errors.
  • Publish Step: The single red job was publish, which failed with:
    Branch "bump-versions-20260830" is not allowed to deploy to github-pages due to environment protection rules.
    This is expected and intended: deployment to GitHub Pages is restricted by environment rules to main. When merged to main, the post-merge push event will execute publish with valid permissions.

5. Negative Control / Red-Test

  • Mutation Sensitivity:
    Mutated versions.env with NETCODE_VERSION=99.99.99. Running ./scripts/check-releases.sh immediately caught the invalid pin:
    netcode: pinned 99.99.99, latest 1.4.8
    exit_code=1
    
  • Sync Sensitivity:
    Applied ./scripts/check-releases.sh --update and re-ran ./scripts/check-releases.sh: confirmed output all pinned versions are current with exit code 0.
  • Verified working tree restored cleanly to 6c4a15d0565d21fc294a287d53c002841f5c556d.

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

This branch had an error being deployed

1 failed deployment
github-pages 6c4a15d0 Deployed Aug 30, 2026 by github-actions[bot] via publish #72
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