Skip to content

chore: Configure Renovate#21

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure
Open

chore: Configure Renovate#21
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented May 13, 2026

Copy link
Copy Markdown

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


Detected Package Files

  • Dockerfile (dockerfile)
  • .github/workflows/release.yaml (github-actions)
  • package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title

What to Expect

With your current configuration, Renovate will create 24 Pull Requests:

chore(deps): update dependency eslint-config-prettier to v10.1.8
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-config-prettier-10.x-lockfile
  • Merge into: main
  • Upgrade eslint-config-prettier to 10.1.8
chore(deps): update dependency semantic-release to v24.2.9
  • Schedule: ["at any time"]
  • Branch name: renovate/semantic-release-monorepo
  • Merge into: main
  • Upgrade semantic-release to 24.2.9
chore(deps): update aws-sdk-js-v3 monorepo to v3.1045.0
chore(deps): update dependency @​modelcontextprotocol/sdk to v1.29.0
  • Schedule: ["at any time"]
  • Branch name: renovate/modelcontextprotocol-sdk-1.x-lockfile
  • Merge into: main
  • Upgrade @modelcontextprotocol/sdk to 1.29.0
chore(deps): update dependency @​types/node to v22.19.19
  • Schedule: ["at any time"]
  • Branch name: renovate/node-22.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 22.19.19
chore(deps): update dependency eslint to v9.39.4
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: main
  • Upgrade eslint to 9.39.4
chore(deps): update dependency eslint-plugin-prettier to v5.5.5
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-prettier-5.x-lockfile
  • Merge into: main
  • Upgrade eslint-plugin-prettier to 5.5.5
chore(deps): update dependency inquirer to v12.11.1
  • Schedule: ["at any time"]
  • Branch name: renovate/inquirer-12.x-lockfile
  • Merge into: main
  • Upgrade inquirer to 12.11.1
chore(deps): update dependency prettier to v3.8.3
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x-lockfile
  • Merge into: main
  • Upgrade prettier to 3.8.3
chore(deps): update dependency typescript to v5.9.3
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-5.x-lockfile
  • Merge into: main
  • Upgrade typescript to 5.9.3
chore(deps): update typescript-eslint monorepo to v8.59.3
chore(deps): update actions/checkout action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: main
  • Upgrade actions/checkout to v6
chore(deps): update actions/setup-node action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-6.x
  • Merge into: main
  • Upgrade actions/setup-node to v6
chore(deps): update dependency @​types/mime-types to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/mime-types-3.x
  • Merge into: main
  • Upgrade @types/mime-types to ^3.0.0
chore(deps): update dependency eslint to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: main
  • Upgrade eslint to ^10.0.0
chore(deps): update dependency node to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade node to 24
  • Upgrade node to 24-alpine
  • Upgrade @types/node to ^24.0.0
chore(deps): update dependency semantic-release to v25
  • Schedule: ["at any time"]
  • Branch name: renovate/major-semantic-release-monorepo
  • Merge into: main
  • Upgrade semantic-release to ^25.0.0
chore(deps): update dependency typescript to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-6.x
  • Merge into: main
  • Upgrade typescript to ^6.0.0
chore(deps): update docker/build-push-action action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-build-push-action-7.x
  • Merge into: main
  • Upgrade docker/build-push-action to v7
chore(deps): update docker/login-action action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-login-action-4.x
  • Merge into: main
  • Upgrade docker/login-action to v4
chore(deps): update docker/setup-buildx-action action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-setup-buildx-action-4.x
  • Merge into: main
  • Upgrade docker/setup-buildx-action to v4
chore(deps): update docker/setup-qemu-action action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-setup-qemu-action-4.x
  • Merge into: main
  • Upgrade docker/setup-qemu-action to v4
chore(deps): update jest monorepo to v30
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jest-monorepo
  • Merge into: main
  • Upgrade @types/jest to ^30.0.0
  • Upgrade jest to ^30.0.0
fix(deps): update dependency inquirer to v13
  • Schedule: ["at any time"]
  • Branch name: renovate/inquirer-13.x
  • Merge into: main
  • Upgrade inquirer to ^13.0.0

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.


❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


This PR was generated by Mend Renovate. View the repository job log.


Note

Low Risk
Low risk: adds a standard renovate.json config file only; no runtime code or dependency versions are changed.

Overview
Adds renovate.json extending config:recommended, enabling Renovate to start managing dependency update PRs for the repo once merged.

Reviewed by Cursor Bugbot for commit 5803e90. Bugbot is set up for automated code reviews on this repo. Configure here.

@greptile-apps

greptile-apps Bot commented May 13, 2026

Copy link
Copy Markdown

Greptile Summary

This PR onboards Renovate for automated dependency management by adding a minimal renovate.json with the config:recommended preset.

  • Adds renovate.json with no custom overrides beyond the recommended defaults, which will trigger 24 dependency update PRs after merging covering npm packages, GitHub Actions, and Dockerfile base images.
  • No application code is changed; merging this PR simply activates Renovate on the repository.

Confidence Score: 5/5

Safe to merge — adds only a single JSON config file with no changes to application code.

The change is a single 6-line JSON file using Renovate's well-known recommended preset. No logic, no application code, and no sensitive configuration is touched.

No files require special attention.

Important Files Changed

Filename Overview
renovate.json Adds Renovate configuration with the default config:recommended preset to enable automated dependency updates.

Reviews (1): Last reviewed commit: "Add renovate.json" | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants