-
-
Notifications
You must be signed in to change notification settings - Fork 31
Paket to nuget #289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paket to nuget #289
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR migrates MiniScaffold from Paket to NuGet's Centralized Package Management, removing Paket dependency management in favor of NuGet's newer centralized approach using Directory.Packages.props files.
Key changes:
- Replaces Paket with NuGet's Centralized Package Management
- Removes all paket.dependencies, paket.references, and paket.lock files
- Adds NuGet.config and Directory.Packages.props files for centralized package version management
Reviewed Changes
Copilot reviewed 48 out of 53 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| paket.dependencies | Removes root paket dependencies file |
| Directory.Packages.props | Adds centralized package version management |
| NuGet.config | Adds NuGet configuration with package source mapping |
| build/build.fs | Updates publish logic from Paket.push to NuGet.NuGetPublish |
| tests/MiniScaffold.Tests/*.fsproj | Replaces paket.references with PackageReference elements |
| Content/Library/* | Updates template files to use NuGet centralized management |
| Content/Console/* | Updates console template to use NuGet centralized management |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
## [0.39.0-beta001] - 2025-09-01 ### Changed - [Paket to Nuget](#289) from @TheAngryByrd - [Update fantomas version to 7.0.3](#290) from @TheAngryByrd - [Update GitHub Actions to use latest action versions](#291) from @TheAngryByrd
## [0.39.0-beta002] - 2025-09-01 ### Changed - [Paket to Nuget](#289) from @TheAngryByrd - [Update fantomas version to 7.0.3](#290) from @TheAngryByrd - [Update GitHub Actions to use latest action versions](#291) from @TheAngryByrd
## [0.39.0] - 2025-09-01 ### Changed - [Paket to Nuget](#289) from @TheAngryByrd - [Update fantomas version to 7.0.3](#290) from @TheAngryByrd - [Update GitHub Actions to use latest action versions](#291) from @TheAngryByrd
Proposed Changes
Removes paket in favor of nuget's Centralized Package Management. Even though there still isn't a solution level lock file, it really only matters for applications. Libraries needing a centralized lock file is a bit less of a concern.
Types of changes
What types of changes does your code introduce to MiniScaffold?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...