Skip to content

Configure Renovate - #30

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

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

Conversation

@renovate

@renovate renovate Bot commented Oct 1, 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/build-and-deploy-on-merge.yaml (github-actions)
  • .github/workflows/build-on-feature-branch.yaml (github-actions)
  • .github/workflows/deploy-feature-branch.yaml (github-actions)
  • .github/workflows/lint.yml (github-actions)
  • .github/workflows/publish-docker-images.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.
  • Update vulnerable PHP runtime pins for CVE-2026-109618 and CVE-2026-109619.
  • 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
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs

What to Expect

With your current configuration, Renovate will create 10 Pull Requests, up to a maximum of 21 over time (see docs for prConcurrentLimit), plus 1 security update Pull Request which is not subject to this limit:

Update dependency zod to v4 [SECURITY]
  • Branch name: renovate/npm-zod-vulnerability
  • Merge into: main
  • Upgrade zod to sha512-4UmzQUF5fxvfcYHlbjBmejU+w+hbDnWFx4aS8kBx7nPBHcO2SqPbpAG8snbdg+Xse4pRefR98hgjFgIMCI/UhA==
Update eslint monorepo to v9.39.5
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: main
  • Upgrade @eslint/js to 9.39.5
  • Upgrade eslint to 9.39.5
Update dependency @​tigerdata/mcp-boilerplate to ^0.9.0
  • Schedule: ["at any time"]
  • Branch name: renovate/tigerdata-mcp-boilerplate-0.x
  • Merge into: main
  • Upgrade @tigerdata/mcp-boilerplate to sha512-PqTFUrqh3w4xd+K6HugVonq36NoIdhEoG4cWIKQwX/vaI84qMNgWD/DeZRsqG5IRYHolS9HY1i3rJnT1RPyjNw==
Update dependency @​types/node to v22.20.5
  • Schedule: ["at any time"]
  • Branch name: renovate/node-22.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 22.20.5
Update dependency dotenv to v17.4.2
  • Schedule: ["at any time"]
  • Branch name: renovate/dotenv-17.x-lockfile
  • Merge into: main
  • Upgrade dotenv to 17.4.2
Update dependency prettier to v3.9.10
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x-lockfile
  • Merge into: main
  • Upgrade prettier to 3.9.10
Update dependency tsx to v4.23.15
  • Schedule: ["at any time"]
  • Branch name: renovate/tsx-4.x-lockfile
  • Merge into: main
  • Upgrade tsx to 4.23.15
Update dependency typescript-eslint to v8.72.1
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-eslint-monorepo
  • Merge into: main
  • Upgrade typescript-eslint to 8.72.1
Update actions/checkout action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-7.x
  • Merge into: main
  • Upgrade actions/checkout to v7
Update actions/setup-node action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-7.x
  • Merge into: main
  • Upgrade actions/setup-node to v7
Update dependency @​linear/sdk to v101
  • Schedule: ["at any time"]
  • Branch name: renovate/linear-sdk-101.x
  • Merge into: main
  • Upgrade @linear/sdk to sha512-pQMaZmh/ewEMR9QmSZDuY+5NQy+xYS3DJDjqLEqlqj35M71Xde9vMHuNijamDZGqG6CojtCSU6YjgIg14pw+1A==
Update dependency @​tigerdata/mcp-boilerplate to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/tigerdata-mcp-boilerplate-2.x
  • Merge into: main
  • Upgrade @tigerdata/mcp-boilerplate to sha512-B3fMHal1OUVyhwlvuqOfC6cN+E9cXWikJLZ2sZbHRi+A3wVn33kqmZqbTLClRkg12ewsXI2OVes5y4Sx5Khb9g==
Update dependency dotenv to v18
  • Schedule: ["at any time"]
  • Branch name: renovate/dotenv-18.x
  • Merge into: main
  • Upgrade dotenv to sha512-3fVOW4cB02R066PUSwn8O4TJyz9NckQl7F81blIbaq9jKBm2tSmOKky7ZHIXzGvkVPXCSn6jkpziBPZdGFs8Tw==
Update dependency node to v26
  • Schedule: ["at any time"]
  • Branch name: renovate/node-26.x
  • Merge into: main
  • Upgrade node to 26
  • Upgrade node to 26-alpine
  • Upgrade @types/node to sha512-MzQj+8Kx3XI40OmUAE6Qoh58ZMNstNNMwn2nfd3qWsfe7nDNSqJNzes4njhz6AHwrSHOffSLwXU6yb474Q4aog==
Update dependency typescript to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-7.x
  • Merge into: main
  • Upgrade typescript to sha512-8FYau96o3NKOhbjKi/qNvG/W5jhzxkbdm5sj9AbZ/5T5sWqn3hJgLfGx27sRKZWTvyzCP8dLRBTf5tBTSRVUNA==
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
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
Update docker/metadata-action action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-metadata-action-6.x
  • Merge into: main
  • Upgrade docker/metadata-action to v6
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
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
Update eslint monorepo to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: main
  • Upgrade @eslint/js to sha512-zeR9k5pd4gxjZ0abRoIaxdc7I3nDktoXZk2qOv9gCNWx3mVwEn32VRhyLaRsDiJjTs0xq/T8mfPtyuXu7GWBcA==
  • Upgrade eslint to sha512-T0pNsxkb9IKmtQjhpK3d7nWOpFv+YHuMbTJnSVMoQblF0onvXfErrtp4V1jHtsQPan7dKaGVD0q1WCXnzMF31A==

🚸 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. Security update Pull Request is not subject to this limit and will be created straight away.


❓ 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.

@renovate
renovate Bot requested a review from a team as a code owner October 1, 2026 17:31
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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.

1 participant