dependency-version-selectionlisted

# Dependency Version Selection Select current releases from live evidence, then make the resulting build reproducible. A version remembered by the model, copied from a template, or shown in an old example is never version-selection evidence. Read [registry resolution](references/registry-resolution.md) for the relevant package ecosystem. Read [runtime channels](references/runtime-channels.md) when selecting a language runtime, compiler, SDK, or toolchain. ## Method 1. Inspect the active technology profile, manifests, lockfiles, runtime and platform constraints, package type, and current dependency graph. Separate genuine constraints from versions that are merely already installed. 2. Query the affected dependency set at its authoritative release source during this task: every direct dependency for project bootstrap or a currency review, and the changed package plus its coupled runtime, framework, generator, plugin, and peer set for a bounded addition. Record the source, observation time, stable channel, current stable release, deprecation or withdrawal state, and material engine or peer constraints. 3. Select the newest eligible stable production release. For a new project, shape the project around that release. For an existing project, cross the major-version boundary and perform the migration by default; do not stop at the newest version admitted by an obsolete manifest range. 4. Resolve a coherent set. Upgrade the runtime, framework, offic