Skip to content

feat(release): Code-Exec is a release-train node (chain leg in ci.yml, train-only releases) - #16

Merged
IvanMurzak merged 3 commits into
mainfrom
feat/release-train-node
Nov 14, 2026
Merged

IvanMurzak merged 3 commits into
mainfrom
feat/release-train-node

Conversation

@IvanMurzak

Copy link
Copy Markdown
Owner

Code-Exec becomes a node of the ai-game-dev release train (code-exec), so it releases only through the train, like every other internal package, and its consumers get cascaded updates (owner request).

What changes

  • ci.yml: workflow_dispatch takes the chain lock / lock_hash8; with a lock the run is named chain <h8> code-exec and keyed on the lock. The package job is the chain leg: it resolves Python, runs chain_feed.py apply --node code-exec --job package, and (only under a lock) packs both packages at the lock's ws version into .artifacts/nuget, then records and uploads chain-leg-*. Without a lock every chain step is a no-op and CI is unchanged.
  • scripts/pack.sh [out-dir] [msbuild args...]: extra args go to both dotnet pack calls; -p:Version=<v> also names the files the shape check opens.
  • .github/scripts/chain_feed.py: vendored v12 (never edit it here).
  • python/code_exec/__init__.py: __version__ was 0.4.0 while the packages are 0.4.1. It is now the props version, a train lockstep file, and a test pins the two together.
  • AGENTS.md, README.md and the release.yml header: releases go only through the train, never a manual dry_run=false dispatch.

Verification (local)

  • scripts/pack.sh <dir> -p:Version=0.4.1-ws.g2f46b502: both nupkgs land where record looks. The leg's own-pack proofs are OK: the Core's ProductVersion is 0.4.1-ws.g2f46b502+2f46b50…, and the source-only Roslyn package's nuspec <version> matches.
  • python -B -m unittest discover -s python/tests passes on Python 3.13 (73 tests). The new version test passes.
  • Stages: implementation, simplify: (re-vendored script), code review: (two report-only reviewers; fixes listed in the commit).

Software side: the manifest node, the train edit plans and the relock live in the ai-game-dev-software PR (linked from there). Merge order: this PR and the four consumer re-vendor PRs land on main before the first train that moves Code-Exec. The train's leg-compatibility check refuses that train until then.

🤖 Generated with Claude Code

IvanMurzak and others added 3 commits November 14, 2026 01:25
…chain leg

Owner-approved: Code-Exec releases only through the ai-game-dev release train (node `code-exec`), like every other internal package, so its consumers get cascaded updates.

- ci.yml: workflow_dispatch takes the chain lock; the `package` job resolves Python, runs chain_feed.py apply,
  packs both packages at the lock's ws version into .artifacts/nuget and uploads the leg record.
- scripts/pack.sh takes MSBuild args after the output dir (-p:Version=<ws> for the chain leg).
- .github/scripts/chain_feed.py vendored (v12).
- AGENTS.md, README.md and the release.yml header: releases go only through the train, never a manual dispatch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The canonical script's simplify pass (one fresh_clone for lower nodes and vendored producers); behaviour unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ndored

Two report-only reviewers (high). Fixed:
- python/code_exec/__init__.py said __version__ 0.4.0 while the packages are 0.4.1; nothing moved it. It is now the
  props version, a release-train lockstep file, and a test pins the two together.
- .github/scripts/chain_feed.py re-vendored: a vendored producer is always a fresh clone.
Not changed: scripts/pack.sh reads only the -p:Version= spelling (the chain always passes that form).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@IvanMurzak
IvanMurzak merged commit 61c61da into main Nov 14, 2026
13 checks passed
@IvanMurzak
IvanMurzak deleted the feat/release-train-node branch November 14, 2026 10:01
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