Back to Blogs
#antigravity#renovate#development

Maintaining open source projects up to date with Renovate and Antigravity

Renovate Renovate is a tool I really appreciate. I wrote a blog post about it and gave a...

3 min read
Cover for Maintaining open source projects up to date with Renovate and Antigravity

Renovate

Renovate is a tool I really appreciate. I wrote a blog post about it and gave a talk on it with Lise Quesnel, which we had the opportunity to present at several conferences (such as Devoxx France 2025). This tool detects new versions of your dependencies and suggests updating them via Pull Requests (PR) or Merge Requests (MR). It is very practical for keeping dependencies up to date and automatically receiving security patches as soon as they are released.

Hacktoberfest and grouping my projects

Before this year's Hacktoberfest (a famous open source event), I wanted to gather all my open source projects into a GitLab group. The first step was to configure Renovate running regularly. Personally, I chose to schedule it every Monday morning.

My main challenge was reviewing Merge Requests every week to avoid accumulating technical debt. My Renovate setup automatically merges MRs for patch or minor updates, provided the CI/CD pipeline passes without errors. For major versions, I prefer to keep manual oversight for now, as they often bring significant changes that require dedicated attention.

While MRs are merged automatically, receiving multiple MRs in a single Renovate run means several open MRs across projects. As soon as one is merged, others become outdated relative to the main branch: they need to be rebased and their pipelines rerun, which Renovate won't do until its next scheduled run. Grouping minor and patch updates into a single MR is an option, but a single failing dependency would then block the entire batch.

First step: merge trains

To manage this flow, the first step was adopting GitLab's Merge Trains. Available on Ultimate plans, this feature queues MRs set to auto-merge. GitLab automatically rebases branches and integrates them one by one without breaking the build.

Agents to the rescue?

I figured there was automation potential here. In the AI era, I wondered if creating a scheduled task in Antigravity to handle MRs was the solution. It's feasible, but would require Antigravity to act as a superuser with rights to merge MRs independently. Delegating such tasks to AI feels unnecessary when checking pipeline status and triggering merges can be handled by a simple script without consuming tokens on every execution.

Instead, I opted for an application that:

  • retrieves projects listed in a configuration file;
  • checks MR statuses for each project using glab (GitLab CLI);
  • enables auto-merge via glab for MRs with passing pipelines.

Where does Antigravity fit in?

When a pipeline fails, Antigravity steps in. I built an app that invokes the Antigravity CLI, fetches the branch locally, analyzes the CI error, and attempts a fix. If the fix succeeds and the pipeline passes, it merges the MR. Unlike the initial idea, the AI agent intervenes only when a pipeline fails—where intelligent analysis adds real value. Everything else remains governed by deterministic code.

The application is written in Go. Although an official Antigravity Go SDK is not yet available, the CLI fulfills the requirements seamlessly.

To ensure a smooth user experience, I added a Mac GUI showing ongoing tasks and prompting for user approval when Antigravity agents require validation. For visual flair, agents are depicted as characters/robots reflecting their current state:

  • idle;
  • active;
  • overworked;
  • or awaiting user validation.

Différents états du robot représentant l'agent Antigravity

This application enables swift resolution of open source project updates while retaining full oversight. Running continuously, it activates upon session unlock to monitor Renovate MRs across repositories 🙌.

Interface de l'application OSS Helper montrant les agents actifs

Liste des Merge Requests Renovate dans OSS Helper

Technical prerequisites

To run the application, the following setup is required:

  • macOS;
  • glab (GitLab CLI), installed and authenticated;
  • Antigravity CLI, installed and authenticated.

My new open source tool 🙌

In this setup, each component serves a dedicated purpose:

  • Renovate identifies updates;
  • GitLab merge trains integrate them cleanly;
  • Go orchestrates execution;
  • Antigravity intervenes specifically when failures require root-cause analysis.

Future enhancements will introduce GitHub and Dependabot support to cover repositories hosted on GitHub as well.

👉 Project repository on GitLab: https://gitlab.com/jeanphi-baconnais-oss/oss-helper.