target-new-framework

Automate a .NET major version bump by updating eng/Versions.props, Directory.Build.props, workload manifests, and related documentation. The workflow applies to netN to netN+1 upgrades across build configurations, templates, tests, and docs using a phased discovery and execution process.

Upgrading Target Framework Monikers requires updating Directory.Build.props and related build configurations. You must also synchronize core version properties in eng/Versions.props, including MajorVersion, ProductVersion, and SDK bands, to maintain repository consistency during the major version bump.

Align frozen workload manifests for previous netN versions by creating and updating manifest registrations when explicit lists are used. This ensures workload manifests remain synchronized with the new major version and correctly reference the updated SDK bands and product version properties.

The dotnet version bump workflow propagates changes to templates, test assets, and documentation to reflect the new version. This ensures total repository consistency by verifying that all related files are updated alongside the core version properties and target framework monikers.

This automation is designed specifically for major netN to netN+1 upgrades across the repository. It applies a phased discovery and execution process with verification steps and safe defaults to handle the complexity of major version bumps, rather than minor version updates.

Automating dotnet major version bumps requires careful handling of explicit manifest lists and frozen workload manifests for previous versions. While the process includes verification steps and safe defaults, you must manually verify phased discovery results to ensure all templates and test assets are correctly propagated.