How to Get Package Updates in Hard-to-Reach Places With RenovateBot
Sean Killeen

Sean Killeen @seankilleen

About: A mind at work. Microsoft MVP && Passionate .NET dev lead && VP, Innovation and Products at SCT Software. Opinions here are mine. Trying to be all the human I can be with the time I have.

Location:
Arlington, VA
Joined:
Dec 27, 2017

How to Get Package Updates in Hard-to-Reach Places With RenovateBot

Publish Date: Jan 20
0 0

Background

I’ve adopted RenovateBot in many of my repositories. I’ve found it easier to work with than GitHub’s own Dependabot. Highly recommend checking them and Mend.io (their parent company) out.

A challenge I’ve had in a few places has been that package updater tools aren’t always able to detect every location for packages. For example:

  • In the NUnit Docs repository, we have a reference to the version of NUnit in a build script variable
  • In an automated test in a company repo that uses TestContainers for .NET, our tests need to use the same version our app does, but the version number is located in a string in the middle of a test.

Luckily, RenovateBot has a great way to manage these too!

Solution: Custom Managers

Read more at SeanKilleen.com!

Comments 0 total

    Add comment