Skip to content

Fix CI fuzzer restore isolation, pack versioning consistency, and NuGet push branch gating#5

Closed
Copilot wants to merge 2 commits into
dev/mkrueger/workflowsfrom
copilot/sub-pr-4
Closed

Fix CI fuzzer restore isolation, pack versioning consistency, and NuGet push branch gating#5
Copilot wants to merge 2 commits into
dev/mkrueger/workflowsfrom
copilot/sub-pr-4

Conversation

Copy link
Copy Markdown

Copilot AI commented Mar 20, 2026

Three independent correctness issues in the GitHub Actions and Azure Pipelines CI configuration identified in code review.

Changes

  • ci.yml – fuzzer smoke test: Added --no-restore to dotnet run so the step can't silently re-restore using the default nuget.config (ADO feed) instead of .github/nuget.github.config.

  • package-unsigned.yml – pack versioning: Removed --no-build from dotnet pack and added Version, FileVersion, and InformationalVersion properties. Previously the pack reused binaries from the unversioned Build solution step, producing packages where the NuGet package version differed from the embedded assembly version.

  • CosmosDB-Shell-Official.yml – version normalization: Added $buildNumber = $version after the updatebuildnumber call so $infoVersion is constructed from the normalized version rather than the original Build.BuildNumber.

  • CosmosDB-Shell-Official.yml – NuGet push gating: Changed both push step conditions from succeeded() to and(succeeded(), eq(variables['Build.SourceBranch'], 'refs/heads/main')) to prevent packages being pushed from feature or PR branches.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

…h gating

Co-authored-by: mkrueger <341098+mkrueger@users.noreply.github.com>
Copilot AI changed the title [WIP] Add GitHub workflows for building Fix CI fuzzer restore isolation, pack versioning consistency, and NuGet push branch gating Mar 20, 2026
Copilot AI requested a review from mkrueger March 20, 2026 11:51
@mkrueger mkrueger closed this Mar 20, 2026
@mkrueger
Copy link
Copy Markdown
Contributor

duplicate #6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants