Configure Renovate

[confused-Techie]

Added a Renovate configuration similar to the one currently used over on the Pulsar repo.

This will help us stay more on top of the dependencies within this repo automatically.

[DeeDeeG]

Want to think about this one for a tad, since if we actually use this, it could cause quite a bit of traffic around these parts where it's normally pretty slow. I want to think over an be comfortable with how it's going to proceed.

I had some specific thoughts on parts of the config in individual code comments in this thread.

The "node <15" thing I think is a valid suggestion on my part based on this example from the Renovate docs: https://docs.renovatebot.com/configuration-options/#constraints

But if this is how we're doing it in core, kinda makes sense to keep it consistent. If I have a chance to think this over for a bit that'd be great, but wanted to comment on this sooner rather than later just to be clear I wasn't ignoring it, since I've been reviewing everything else here very timely.

P.S. I read these docs to understand the config file, for anyone else curious about what these values all mean: https://docs.renovatebot.com/configuration-options (It was kind of hard to find this, IMO!)

[DeeDeeG]

I lean toward: have a dashboard, but separate the packages out to individual lines so we can see what version it wants to bump to.

And comments above to make the "informational view" the most useful as a guide when looking it over and bumping things manually.

[confused-Techie]

@DeeDeeG Alright, I've taken all of your suggestions.

The dashboard has zero grouping, so we can view each dep individually, even as far as not splitting major minor or anything, so that we get as many different options as possible

[DeeDeeG]

Thanks for taking this feedback.

This works well for me as it's set up now (mostly using defaults, I suppose.)

I wasn't planning to include this in the ppm bump in core, since it's not a code change more of a meta thing, won't affect users in and of itself, but I might as well include it if we do get this in before I do the ppm bump PR. 🤷

Anyway, THANK YOU for all the attention given to this repo lately, it's setting us up to do more good things here, for sure.

[confused-Techie]

Fantastic, lets get it merged in then anyway, but like you said doesn't make much of a difference.

But I'm glad the focus is noticed, thought with those huge blockers out of the way like decaf and async, nows the time to shine on every other change that might be needed or wanted. So hopefully we can get things much more streamlined here