NuKeeper's future

[skolima]

NuKeeper was created when no similar tool existed. It kept on going for quite a while as the main contributors used it daily, but things have changed. With Dependabot being a built in part of GitHub now, and dotnet-outdated available for command line use, NuKeeper mostly remains used for the niche scenarios involving Classic .NET Framework. With .NET 6.0 available, we (@AnthonySteele and @skolima ) feel NuKeeper has fulfilled its purpose.

This issue is a notification we intend to archive this repository and not release any future updates. We're very grateful to all contributors to NuKeeper over the years.

If you do use NuKeeper actively and feel like maintaining it is something you'd like to do, you are more than welcome to fork it.

FYI: tagging contributors with 2 or more commits.
@MarcBruins @MaxMommersteeg @shep1987 @zubivan @slang25 @CrispyDrone @sharpSteff @StephanTuinder @Bouke @Jens-H-Eriksen @cohen990 @Chama-StephanTuinder @rajbos @kwlin @ChrisAnn @david-driscoll @arikalish @cswendrowski @msallin

[shep1987]

Thanks @AnthonySteele and @skolima

I agree the world seems to be moving away from .net framework very quickly so I think this is a sensible move.

Thank you all for your contributions and possibly see you in another Project soon!

[Doug-Murphy]

I stumbled upon this repo 2 days ago and found it fit my needs perfectly. My company uses Bitbucket Server for our code, so we can't use Dependabot. Looking at dotnet-outdated, I'm not seeing any mention of functionality to open PRs for the updates. It appears to be a local-only tool. What replacement do you recommend for the scenario of wanting PRs opened automatically for NuGet package updates to a Bitbucket Server instance?

[arikalish]

My company uses Bitbucket Server for our code, so we can't use Dependabot.

I'm in the same boat. We're running local builds with a few modifications (see my open PRs in this repo). We'll be keeping going with the latest version until we have time to build a tool that wraps dotnet-outdated and creates PRs in BitBucket based on its output. Thankfully, the BitBucket APIs aren't terribly complex, but it's not on our radar until NuKeeper stops working for our use case.

[skolima]

We're not planning on taking down the existing tool, it will continue to work as it does currently. We're just acknowledging the fact that we have stopped maintaining it.

[Doug-Murphy]

@skolima I understand that, but with no maintenance it eventually will become unusable. :) That's why I'm looking for a replacement if one currently exists.

[rajbos]

Also have a look at Renovate that has lots of integrations to the SCM systems mentioned above. And I you need to, most tools can run inside a container as well 😉.

[slang25]

I would like to see NuKeeper continue to be maintained and used by the community. If I'm honest, I don't have enough energy to do it, and we would need someone who has that energy.

@msallin you expressed interest recently in being involved, what are your thoughts?

Perhaps we can put out a call for new maintainers on Twitter too?

[Bouke]

@AnthonySteele and @skolima thank you so much for this tool. It has been a great help for some time.

I'm currently not in a position to take on the maintenance of this tool. It has been disabled at my $company for some time now due to blocking issues and I don't see those resolved soon either.

Now that this project might go archived, may I suggest you disable the stale bot on this repository? That would allow future potential users/maintainers to evaluate the state of the project and the issues tab would be a good representation of any current issues.

[AnthonySteele]

The project is now archived. You are welcome to fork it.
We did not opt for handling over the maintenance and the urls on NuGet and Docker, as NuKeeper is a part of the build chain, and thus potentially a very juicy target for an attack. We do want anyone moving to a new tool, under new maintainers, to have to perform the switch explicitly.