Skip to content
This repository has been archived by the owner on Nov 7, 2023. It is now read-only.
/ NuKeeper Public archive
forked from NuKeeperDotNet/NuKeeper

Automagically update nuget packages in .NET projects

License

Notifications You must be signed in to change notification settings

CrispyDrone/NuKeeper

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

NuKeeper

Automagically update NuGet packages in all .NET projects.

This fork includes additional features and fixes that have not been integrated in the main repository of NuKeeper at the time of writing. This fork is only intended to temporarily bridge this gap. As soon as NuKeeper provides the same benefits, this fork can be deleted.

Additional features:

  • Support --reviewer for Azure Devops Services/Azure Devops Server/TFS for all commands that create pull requests

  • Support --maxopenpullrequests for AzureDevops/TFS for all commands that create pull requests

  • Support custom templates for commit messages, pull request title, and pull request body. The templates can be specified in mustache, we use the Stubble engine.

  • Support --targetBranch for Azure Devops while using the repository command and providing a remote url

  • Support --targetBranch for TFS while using the repository command and providing a remote url Now included in nukeeper.

  • Fixed issue with --change minor or --change patch resulting in incorrect major or minor updates when multiple versions installed in different projects already differ in minor or major versions. Now included in nukeeper.

Additional fixes:

  • Ensure NuGet applies the lowest available versions for the dependencies of a package instead of the highest. It seems that NuGet doesn't care about target framework, so the Highest strategy has a high likelihood of failing if you haven't migrated to the latest major versio

    This is a short term fix, in the long term NuKeeper should take into account the target framework of packages, or if this is a bug in NuGet, it will hopefully be fixed.

  • Ensure NuKeeper retries creating a PR in a next run if it failed.

How To Build and Run From Source

You can install the nukeeper dotnet tool of current build using the InstallNuKeeperDotNetTool (.bat for Windows, .sh for macOS and Linux) found in the root of the repository.

Note: this overrides your existing global installation of the NuKeeper dotnet tool.

You can build and package the tool using the following commands. The instructions assume that you are in the root of the repository.

dotnet pack .\NuKeeper\NuKeeper.csproj -o ".\artifacts"
dotnet tool install nukeeper --global --add-source ".\artifacts"
nukeeper --version

Note: On macOS and Linux, .\NuKeeper\NuKeeper.csproj and .\artifacts will need be switched to ./NuKeeper/NuKeeper.csproj and ./artifacts to accommodate for the different slash directions.

Licensing

NuKeeper is licensed under the Apache License

Acknowledgements

About

Automagically update nuget packages in .NET projects

Resources

License

Code of conduct

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C# 88.2%
  • CSS 5.7%
  • JavaScript 3.2%
  • HTML 2.9%
  • Shell 0.0%
  • Batchfile 0.0%