harden(go-migration): require upstream APM freshness#121
Conversation
Migration Benchmark Results
Migration CLI BenchmarkIncludes fixture-backed commands that must read, write, execute, or fail against real project state. The installed-project fixture contains apm.yml, apm.lock.yaml, apm_modules packages, local .apm primitives, target directories, deployed prompt files, and sample source files. Max allowed Go/Python median ratio:
Workloads
|
|
@copilot fix ci |
…nt checks Co-authored-by: mrjf <180956+mrjf@users.noreply.github.com>
Migration Benchmark Results
Migration CLI BenchmarkIncludes fixture-backed commands that must read, write, execute, or fail against real project state. The installed-project fixture contains apm.yml, apm.lock.yaml, apm_modules packages, local .apm primitives, target directories, deployed prompt files, and sample source files. Max allowed Go/Python median ratio:
Workloads
|
Description
Harden migration parity enforcement by requiring upstream APM freshness/contract coverage during enforcing runs.
Follow-up CI fix: updated the migration workflow unit test to match the current env-based enforcement logic in
.github/workflows/migration-ci.yml(manualenforce_completioninput andcrane/*branch detection).Type of change
Testing