This project uses Renovate with a GitHub App for automated dependency management. The configuration is standardized across all eero-ecosystem repositories.

The dependency update system automatically:

• Tracks new releases of eero-api (the core API client), capped below 9.0.0
• Tracks the pinned VictoriaMetrics binary (Dockerfile) via GitHub releases
• Tracks the documented eero-prometheus-exporter image tag in the optional, commented-out compose service
• Creates PRs immediately when dependencies have updates available
• Auto-merges minor/patch updates for non-critical dependencies
• Requires manual review for eero-api and major updates
• Triggers instantly when eero-api releases a new version

Since 6.0 the exporter is not a dependency of eero-ui — it appears in Renovate only as a documented image tag (see Custom Managers).

The Renovate configuration is standardized across all repositories:

eero-prometheus-exporter is a separate project with its own Renovate setup; it is no longer part of eero-ui's dependency chain.

flowchart TB
    subgraph eero-api ["🔧 eero-api"]
        release["🚀 Release v1.3.0"]
        notify["🔔 notify-downstream job"]
        release --> notify
    end

    subgraph dispatch ["repository_dispatch"]
        event["event: eero-api-dependency-update-available"]
    end

    notify --> event

    subgraph downstream ["Downstream Repositories"]
        subgraph ui ["eero-ui"]
            ui_renovate["🔄 Renovate Workflow"]
            ui_pr["📝 Create PR"]
            ui_ci["🧪 CI Pipeline"]
            ui_renovate --> ui_pr --> ui_ci
        end

        subgraph cli ["eero-cli"]
            cli_renovate["🔄 Renovate Workflow"]
            cli_pr["📝 Create PR"]
            cli_ci["🧪 CI Pipeline"]
            cli_renovate --> cli_pr --> cli_ci
        end
    end

    event --> ui_renovate
    event --> cli_renovate

    ui_ci --> review["👀 Manual Review"]
    cli_ci --> review

    review --> merge["✅ Merge"]

    subgraph regex ["eero-ui custom.regex managers (scheduled, not dispatched)"]
        vm["🔷 VictoriaMetrics binary<br/>Dockerfile ARG VM_VERSION ← GitHub releases"]
        exp_tag["🔷 exporter image tag<br/>docker-compose.yml commented service ← ghcr.io"]
    end

    vm --> ui_pr
    exp_tag --> ui_pr

All repositories use the same base configuration. See the config files linked above for the full implementation.

When Renovate detects a new eero-api version:

• Commit Message: chore(deps-critical): update eero-api v1.3.0
• Labels: critical, needs-review, eero-api, dependencies
• Reviewers: Automatically assigned to maintainers
• Assignees: Automatically assigned for accountability
• PR Body: Includes review checklist and relevant links

All major version updates (any dependency):

• Labeled with major-update, needs-review
• Automatically request review from maintainers
• Never auto-merged

The VictoriaMetrics binary has no native package manager, so enabledManagers includes custom.regex and customManagers defines one matcher for it:

The ghcr.io/fulviofreitas/eero-prometheus-exporter tag in the commented-out eero-exporter service in docker-compose.yml is not tracked. eero-ui does not run or depend on the exporter, so the tag is only a pointer for operators. A package rule sets enabled: false for it so Renovate never opens PRs for it.

When eero-api releases a new version, it automatically notifies all downstream repositories via repository_dispatch.

sequenceDiagram
    participant EC as eero-api
    participant GH as GitHub
    participant UI as eero-ui
    participant CLI as eero-cli

    EC->>EC: 🚀 Semantic Release
    EC->>GH: notify-downstream job
    
    par Dispatch to all repos
        GH->>UI: repository_dispatch
        GH->>CLI: repository_dispatch
    end

    UI->>UI: 🔄 Renovate runs
    CLI->>CLI: 🔄 Renovate runs

    UI->>UI: 📝 Creates PR
    CLI->>CLI: 📝 Creates PR

The two regex-managed versions (VictoriaMetrics binary, exporter image tag) are picked up on the scheduled and manual runs only; there is no cross-repository dispatch for them.

To run Renovate manually:

1. Go to Actions → 🔄 Renovate
2. Click Run workflow
3. Options:
   • Dry-run mode: Preview changes without creating PRs
   • Log level: Set to debug for troubleshooting
   • Reset cache: Clear cached data for fresh run

Renovate creates a Dependency Dashboard issue that shows:

• All detected dependencies
• Pending updates
• Config warnings
• Manual override checkboxes

The dashboard is auto-closed when there are no more updates (dependencyDashboardAutoclose: true).

You can force-create any PR by checking its checkbox in the dashboard.

Renovate's auto-merge works with the repository's auto-merge workflow:

1. Renovate creates PR with automerge label
2. CI pipeline runs and passes
3. Auto-merge workflow detects the label
4. PR is automatically merged (squash strategy)

The Renovate workflow includes repository caching for faster subsequent runs.

• Retention: 7 days
• Reset cache: Use the "Reset repository cache" option in manual workflow dispatch
• Cache key: renovate-cache-v1 (bump version in workflow to bust cache)