Automatically update NuGet packages in .NET projects across repositories with pull request generation.
NuKeeper is a .NET command-line tool that automates the updating of NuGet package dependencies in .NET projects. It scans for outdated packages, applies updates, and can generate pull requests to streamline dependency management across repositories. The tool supports both .NET Framework and .NET Core projects, including private NuGet feeds.
.NET developers and teams managing multiple repositories who want to automate dependency updates and reduce manual maintenance efforts.
Developers choose NuKeeper for its seamless integration with popular Git platforms, ability to handle private feeds, and automation of pull request generation, making dependency updates more efficient and consistent.
Automagically update nuget packages in .NET projects
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Scans .NET projects for outdated NuGet packages and applies updates automatically, reducing manual effort as described in the README's feature list.
Generates pull requests on supported platforms like GitHub, Azure DevOps, BitBucket, GitLab, and Gitea, enabling seamless workflow automation per the README's platform table.
Offers commands such as inspect, update, repo, org, and global for various update scenarios, from local projects to organization-wide management, detailed in the commands section.
Handles private NuGet feeds, making it suitable for enterprise environments with custom packages, as noted in the platform support table.
The project is archived, with a README link to 'Why is NuKeeper Archived,' meaning no future updates, bug fixes, or compatibility with newer .NET versions.
On Linux and macOS, it requires Mono installation and is labeled as experimental, leading to potential instability and extra setup complexity, as cautioned in the installation notes.
Lacks sophisticated conflict resolution for package updates and may not handle complex dependency graphs well, relying on basic automation without detailed handling mentioned in the README.