Use devVersion OS config when creating new versions

Problem

bakery create version copies the OS list from the latest version. If the devVersion has a different OS config (added OS, dropped OS, changed platforms), the new version won't reflect it.

Dependencies already come from image-level dependencyConstraints. OS config should too — via the devVersion.

Today

bakery create version connect 2026.03.0 --subpath 2026.03

• OS list: copied from latest version
• Dependencies: resolved from image-level constraints

Proposal

• OS list: copied from devVersion
• Fallback: copy from latest if no devVersions exist
• Multiple devVersions: use the first (or require consistent OS lists)

Caveat: platforms may differ

devVersion OS entries often omit platforms (defaults to [amd64]). Release versions may have explicit [amd64, arm64]. Switching to devVersion as the OS source could silently narrow platform support.

Suggested path: use devVersion as-is, and have the release workflow surface OS differences in the PR body so reviewers can catch platform changes.

Related

• #349 — release workflow (parent issue)
• PR #393 — bakery CLI changes for release automation

Start at the bakery create version command and trace how it currently selects the OS list from latest, then inspect how devVersions and image-level dependency constraints are represented. Done means new versions use the selected devVersion OS config, fall back to latest when none exist, and account for the stated multiple-devVersion and platform differences.