Skip to content

fix: configure CLI single-file publishing in project - #40

Merged
ScottishTapWater merged 1 commit into
mainfrom
fix/cli-single-file-publish
Nov 13, 2026
Merged

ScottishTapWater merged 1 commit into
mainfrom
fix/cli-single-file-publish

Conversation

@ScottishTapWater

Copy link
Copy Markdown
Contributor

Change

  • Set single-file publishing in the CLI project for Release builds with a runtime identifier.
  • Extract the full bundle because the CLI runs MSBuild in process and loads assemblies from disk.
  • Remove the duplicate publish flags from CI and release commands. Both commands retain their runtime identifiers and self-contained setting.

Validation

  • dotnet build src/PackageCascade.slnx -c Release
  • dotnet publish src/PackageCascade.Cli/PackageCascade.Cli.csproj -c Release -r linux-x64 --self-contained true -o artifacts/cli -p:DebugType=embedded
  • Published CLI --help and the CI netstandard fixture plan command with its jq -e assertion.
  • MSBuild property check: all three flags are true for Release with linux-x64 and unset for Release without a runtime identifier.

@greptile-apps

greptile-apps Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The PR appears safe to merge.

Summary

Moves single-file publishing settings into the CLI project.

  • Release CLI builds bundle one file and extract all their content.

No actionable issues found.

Reviews (1) · Last reviewed commit: "fix: configure CLI single-file publishin..." · Reviewed by Greptile

@ScottishTapWater
ScottishTapWater merged commit 6d8b0e8 into main Nov 13, 2026
9 checks passed
@ScottishTapWater
ScottishTapWater deleted the fix/cli-single-file-publish branch November 13, 2026 09:41
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.

1 participant