Bump AMX Mod X pin from build 5481 to 5486

[KevinTCoughlin]

Description

The scheduled Version Check workflow (run 35575921362) failed because the pinned AMX Mod X build is behind upstream:

✓  ReHLDS: 3.15.0.896 (up to date)
✓  ReGameDLL_CS: 5.30.0.814 (up to date)
✓  Metamod-R: 1.3.0.149 (up to date)
✓  ReAPI: 5.29.0.358 (up to date)
✗  AMX Mod X: build 5481 → 5486 (update available)

1 component(s) have updates available — please update Containerfile.

This bumps the AMX Mod X pin to build 5486. All four other pinned components are already current, so no other version changes were needed.

Type of Change

• Configuration change
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Infrastructure/CI update

Related Issues

Relates to the failing scheduled version-check.yml run linked above.

Changes Made

• Containerfile: ARG AMXMODX_BUILD 5481 → 5486
• README.md: stack list entry updated to "AMX Mod X 1.10.0 (build 5486)"
• CHANGELOG.md: the two unreleased entries that name the AMX Mod X build resynced to 5486 (they described the same not-yet-released pin, so they were updated in place rather than stacking a second bump entry)

Testing Performed

• Container builds successfully: just build — equivalent verified in CI
• Lint checks pass: just check — verified via the Lint check
• Server starts and is joinable: just up
• Manual testing performed (describe below)

Manual Testing:

www.amxmodx.org is not reachable from the environment these changes were authored in (the egress proxy returns 403 CONNECT tunnel failed), so the new tarballs could not be fetched locally and just build / just check could not be run there. Verification was done in CI instead, which has the network access this needs:

• build-and-scan — success. This is the meaningful check: the Containerfile pulls both AMX Mod X archives with curl -fsSL, so a nonexistent build 5486 would have hard-failed the build on a 404. A green build is direct proof the new tarballs exist, download, and extract. The container smoke test (hlds_linux, hlds_run, entrypoint.sh present and executable) also passed.

• Lint — success. hadolint + shellcheck clean, as expected for a change confined to one pinned value in an existing ARG line.

• Trivy — neutral (scan results uploaded; no failing condition).

• Version Check re-run on this branch — success (run 35641179119), confirming the original failure is resolved:

  ✓  ReHLDS: 3.15.0.896 (up to date)
  ✓  ReGameDLL_CS: 5.30.0.814 (up to date)
  ✓  Metamod-R: 1.3.0.149 (up to date)
  ✓  ReAPI: 5.29.0.358 (up to date)
  ✓  AMX Mod X: build 5486 (up to date)
  
  All components are up to date.
  

Not verified: that the server actually starts and accepts player connections with the new AMX Mod X build. The build and smoke test cover image integrity, not runtime gameplay behaviour, so a quick just up on a host with real network access is worth doing before this is relied on in production.

Checklist

• I have performed a self-review of my own changes
• I have tested that the server starts and accepts connections
• I have updated documentation if needed
• My changes generate no new warnings during build

🤖 Generated with Claude Code

https://claude.ai/code/session_0133c9cteHwTDVAY3TCmt255