mason-registry VS renovate

Can you try to get it added to Mason so people don't have to try and do a custom install?

https://github.com/mason-org/mason-registry/

There was a bug in the new mason registry that I fixed this morning: https://github.com/mason-org/mason-registry/pull/1056

Hello! This is a PSA for people who use mason.nvim (tl;dr at the bottom). Going forward the core registry will be hosted as a collection of static, YAML-based, package definitions at https://github.com/mason-org/mason-registry, as opposed to bundled with the mason.nvim plugin itself as Lua modules. This decouples the infrastructure in such a way that the Lua plugin becomes a standalone client that can be hooked into more registries than just the core one, as well as more easily be subject to versioning (mason.nvim currently doesn't version itself due to the fact that packages are bundled with it, which complicates things). This decoupling also lowers the barrier of entry for additional maintainers who can solely focus on the registry, without having to learn the internals of the plugin (more info will come soon if you're interested in possibly helping maintain the core registry).

Going forward the core mason.nvim package registry will be hosted as a collection of static, YAML-based, package definitions at https://github.com/mason-org/mason-registry, as opposed to bundled with the mason.nvim plugin itself as Lua modules. This will be a fully seamless migration so you shouldn't notice anything and there is no action required. Refer to the full announcement post for more information.

This month, I gave a talk with my Zenika colleague Lise at the DevoxxFR conference about Renovate and Dependabot, two great tools to help you automatize and upgrade your dependencies.

There is no built-in Renovate Bot on a self-hosted GitLab. What can we do to set it up and enjoy all the benefits of automatic dependency updates?

> Yes, it is awesome until you have to sysadmin it, apply updates, patch it, fix security holes, etc. I am not saying all self-hosted solutions are like that. There are exceptions. However, the majority of open-source self-hosted solutions require a lot of extra work.

I'm currently self-hosting 10 different applications on my local server, which represents everything I've ever seen that looked fun or useful to me. Every one of them had a Docker image with an example compose file, which means updating them just requires periodically running Renovate [0] on the repo that stores all my compose files and then running a script that docker compose pulls the updates. It takes maybe 10 minutes every other week, and is actually kinda fun.

It helps that all the apps are only accessible from within my VPN, so I'm not too worried about fixing security updates within a tiny time window.

[0] https://github.com/renovatebot/renovate

This is a big deal! Where did you read this? I found:

https://github.com/renovatebot/renovate/discussions/26917

Renovate is an automated dependency management tool that can be used to keep your dependencies up-to-date. It can be configured to automatically create pull requests to update your dependencies, and it supports a wide range of package managers and platforms.

To get started with Mend Renovate, the comprehensive official documentation provides detailed instructions on installation, configuration, and best practices. Additionally, the Mend Renovate community forum offers a platform for users to connect, share experiences, and access the collective knowledge base.

It is a good practice to keep software up to date. To track changes in upstream software, we can utilize automatic dependency tracking systems such as Dependabot or Renovate. This is a broad topic and requires a separate article to be covered. If you would like to read about it, please vote in the comments section below.

So do other forges: I have Renovate [0] set up on my self-hosted Forgejo and it's worked great so far.

[0] https://github.com/renovatebot/renovate