Skip to content

Fix CI installation of freshly packed tool - #11

Merged
goneflyin merged 1 commit into
mainfrom
goneflyin/10/fix-ci-tool-install
Sep 24, 2026
Merged

goneflyin merged 1 commit into
mainfrom
goneflyin/10/fix-ci-tool-install

Conversation

@goneflyin

Copy link
Copy Markdown
Collaborator

Summary

  • Add a CI-only NuGet config that maps Crap4DotNet to the freshly packed ./nupkg source and maps dependencies to nuget.org.
  • Install with --configfile and --prerelease. Branch builds currently pack an alpha version; without --prerelease, the install does not select that package.

Verification

  • Restored the solution with .NET SDK 8.0.414.
  • Built the CLI in Release and packed Crap4DotNet.0.1.2-alpha.0.1.nupkg.
  • Installed with the new config into a temporary tool path. The install reported version 0.1.2-alpha.0.1, and dotnet-crap --version reported the same version.
  • Confirmed the previous --add-source command selected the published 0.1.1 package on this machine instead of the new alpha package.

Fixes #10.

Use a CI-only NuGet config so Crap4DotNet resolves from the pack output while dependencies remain on nuget.org. Allow prerelease versions because branch builds produce an alpha package; otherwise the install can select the published stable tool.

Fixes #10
@goneflyin
goneflyin force-pushed the goneflyin/10/fix-ci-tool-install branch from 453a56b to ad08a8b Compare September 24, 2026 22:25
@goneflyin
goneflyin merged commit 7630d0e into main Sep 24, 2026
1 check passed
@goneflyin
goneflyin deleted the goneflyin/10/fix-ci-tool-install branch September 24, 2026 22:27
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.

CI: packed tool installation fails with NuGet package source mapping

1 participant