build: migrate versioning to MinVer#261
Draft
ChrisPulman wants to merge 1 commit into
Draft
Conversation
Versioning: - Replace Nerdbank.GitVersioning configuration with MinVer MSBuild properties. - Remove version.json and NBGV package/tool references from the Nuke build. - Keep MinVer centrally versioned and reference it privately from Directory.Build.props. CI: - Remove dotnet/nbgv from BuildOnly. - Rework BuildDeploy into a manual unsigned MinVer release flow with unsigned package artifacts, OIDC NuGet publishing, and GitHub release creation. Validation: - dotnet restore Extensions.Hosting.slnx - dotnet pack Extensions.Hosting.SingleInstance generated 3.2.0-alpha.0.218 - dotnet build Extensions.Hosting.slnx -c Release -warnaserror --no-restore /m:1 - dotnet build ..\\build\\_build.csproj -c Release --no-restore - dotnet test --solution Extensions.Hosting.slnx -c Release --coverage --coverage-output-format cobertura --results-directory .\\TestResults -- --output Detailed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Build and release infrastructure migration.
What is the new behavior?
vtag prefix, a3.2minimum major/minor floor,minorauto-increment, andalpha.0prerelease identifiers for untagged builds.BuildDeploy.ymlis now a manual unsigned release workflow with MinVer version/tag calculation, unsigned NuGet package artifacts, NuGet OIDC trusted publishing, and GitHub release creation.BuildOnly.ymlno longer runs the NBGV action and its test step builds before running MTP/TUnit tests.What is the current behavior?
version.json, Nuke build references, anddotnet/nbgvGitHub Actions steps.Checklist
Additional information
Validation completed locally:
dotnet restore Extensions.Hosting.slnxdotnet pack Extensions.Hosting.SingleInstance\Extensions.Hosting.SingleInstance.csproj -c ReleaseproducedCP.Extensions.Hosting.SingleInstance.3.2.0-alpha.0.218.nupkgdotnet build Extensions.Hosting.slnx -c Release -warnaserror --no-restore /m:1dotnet build ..\build\_build.csproj -c Release --no-restoredotnet test --solution Extensions.Hosting.slnx -c Release --coverage --coverage-output-format cobertura --results-directory .\TestResults -- --output Detailedpassed 352/352This PR intentionally configures the release as unsigned because no signing certificate is available yet. The release workflow expects NuGet trusted publishing via
secrets.NUGET_USER.