Fix GitHub Actions workflow and Azure Pipelines issues from review feedback#6
Merged
Merged
Conversation
Merged
…oning, ADO branch gate, info version fix Co-authored-by: mkrueger <341098+mkrueger@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add GitHub workflows for building
Fix GitHub Actions workflow and Azure Pipelines issues from review feedback
Mar 20, 2026
mkrueger
approved these changes
Mar 20, 2026
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
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.
Several correctness and safety issues in the GitHub Actions and Azure Pipelines workflows identified during review: fuzzer CI could silently pass with crash findings,
dotnet packpayload versioning was inconsistent with the package version, and NuGet push steps in ADO lacked branch/parameter gates allowing unintended publishes from any branch.Changes
.github/workflows/ci.yml--no-restoreto fuzzerdotnet runto prevent a second restore against the wrong NuGet configcrash_*.txtfindings and fails CI if any exist.github/workflows/package-unsigned.ymldotnet packnow passesVersion,FileVersion, andInformationalVersionalongsidePackageVersionso the tool binary metadata inside the nupkg is consistent with the declared package version.pipelines/CosmosDB-Shell-Official.ymlpublishNugetqueue-time boolean parameter and re-addedBuild.SourceBranch == refs/heads/main && publishNuget == trueguard on both NuGet push steps$buildNumberis now updated after normalization soCosmosDBShell_InformationalVersionis derived from the canonical version rather than the pre-normalization valueCONTRIBUTING.md📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.