Written by Jamie Tanna
on 
CC-BY-NC-SA-4.0 AGPL-3.0-only
1 mins

Generating a Renovate Report from someone else's repo

Featured image for sharing metadata for article

As part of Accessing your Renovate Dependency Dashboard, without GitHub/GitLab Issues enabled, I've been trying to represent a Dependency Dashboard based on Renovate's Report functionality.

As I wanted to explore a few more interesting scenarios, I wanted to see how I could get a Report based on i.e. Renovate's Dependency Dashboard or Backstage's Dependency Dashboard as they have all of the key sections used, and some deprecated dependencies to test with, too.

As I don't have access to the infrastructure for these repos' usage of Renovate (via Mend Renovate Cloud), I needed to find an alternative way of calculating the Report.

Through some trial and error, I found that requesting a report, and then using --dry-run=full solved it:

# NOTE that the `--dry-run=full` is required to process which branches Renovate will know about
env RENOVATE_REPORT_TYPE=file RENOVATE_REPORT_PATH=renovate.json npx renovate@40 renovatebot/renovate --dry-run=full

This then gives you the full metadata you need to fully render a Dependency Dashboard, or use it for any other purposes, i.e. with Dependency Management Data.

Written by Jamie Tanna's profile image Jamie Tanna on , and last updated on .

Content for this article is shared under the terms of the Creative Commons Attribution Non Commercial Share Alike 4.0 International, and code is shared under the GNU Affero General Public License v3.0 only.

#blogumentation #renovate.

This post was filed under articles.

Interactions with this post

Interactions with this post

Below you can find the interactions that this page has had using WebMention.

Have you written a response to this post? Let me know the URL:

Do you not have a website set up with WebMention capabilities? You can use Comment Parade.