Refresh full dev-base internal and non-language tool pins #864

Closed
opened 2026-08-04 07:52:19 +00:00 by coilyco-ops · 0 comments
Member

workflow: pull-request-and-merge

Goal

Refresh internal and compatible non-language tools in the full dev-base surface after language payload isolation, without changing or invalidating language runtime payloads.

Confirmed updates

  • Agent Compose 2.0.0 -> 2.1.0
  • Ward 0.864.0 -> 0.869.0
  • specgen 0.128.0 -> 0.131.0
  • AOS 0.148.0 -> 0.152.0
  • Claude Code 2.1.220 -> 2.1.221
  • OpenCode 1.18.9 -> 1.18.12
  • AWS CLI 2.36.11 -> 2.36.15
  • GitHub CLI 2.96.0 -> 2.97.0
  • TruffleHog 3.95.8 -> 3.96.0

Boundaries

  • Do not change Node, Go, .NET, Rust, Python, uv, or Trunk pins.
  • Do not include the Docker CLI 28 -> 29 major upgrade without a separate compatibility decision.
  • Keep all changed pins in the full Dockerfile so the five language payload caches remain reusable.
  • Verify each internal release has both Linux architecture assets and checksums.
  • Run the dev-base contract tests and repository gate. Image-build proof may come from the Docker-changing PR job when the native host has no Docker daemon.

Planner evidence

The current planner can fail every network resolver and still emit an empty successful plan. Treat its output as partial evidence only. Track planner disposition separately rather than implying the inventory is complete.

workflow: pull-request-and-merge ## Goal Refresh internal and compatible non-language tools in the full dev-base surface after language payload isolation, without changing or invalidating language runtime payloads. ## Confirmed updates * Agent Compose 2.0.0 -> 2.1.0 * Ward 0.864.0 -> 0.869.0 * specgen 0.128.0 -> 0.131.0 * AOS 0.148.0 -> 0.152.0 * Claude Code 2.1.220 -> 2.1.221 * OpenCode 1.18.9 -> 1.18.12 * AWS CLI 2.36.11 -> 2.36.15 * GitHub CLI 2.96.0 -> 2.97.0 * TruffleHog 3.95.8 -> 3.96.0 ## Boundaries * Do not change Node, Go, .NET, Rust, Python, uv, or Trunk pins. * Do not include the Docker CLI 28 -> 29 major upgrade without a separate compatibility decision. * Keep all changed pins in the full Dockerfile so the five language payload caches remain reusable. * Verify each internal release has both Linux architecture assets and checksums. * Run the dev-base contract tests and repository gate. Image-build proof may come from the Docker-changing PR job when the native host has no Docker daemon. ## Planner evidence The current planner can fail every network resolver and still emit an empty successful plan. Treat its output as partial evidence only. Track planner disposition separately rather than implying the inventory is complete.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agentic-os#864
No description provided.