Configure Renovate

[renovate]

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

• docker-compose.yml (docker-compose)
• 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
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs

---

What to Expect

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

Update dependency @​subsquid/batch-processor to v0.1.0

• Schedule: ["at any time"]
• Branch name: renovate/subsquid-batch-processor-0.x-lockfile
• Merge into: master
• Upgrade @subsquid/batch-processor to 0.1.0

Update dependency @​subsquid/evm-objects to ^0.0.3

• Schedule: ["at any time"]
• Branch name: renovate/subsquid-evm-objects-0.x
• Merge into: master
• Upgrade @subsquid/evm-objects to ^0.0.3

Update dependency @​subsquid/typeorm-migration to v1.3.1

• Schedule: ["at any time"]
• Branch name: renovate/subsquid-typeorm-migration-1.x-lockfile
• Merge into: master
• Upgrade @subsquid/typeorm-migration to 1.3.1

Update dependency typeorm to v0.3.30

• Schedule: ["at any time"]
• Branch name: renovate/typeorm-0.x-lockfile
• Merge into: master
• Upgrade typeorm to 0.3.30

Update dependency @​subsquid/evm-stream to ^0.1.0

• Schedule: ["at any time"]
• Branch name: renovate/subsquid-evm-stream-0.x
• Merge into: master
• Upgrade @subsquid/evm-stream to ^0.1.0

Update dependency @​subsquid/evm-typegen to v4.6.0

• Schedule: ["at any time"]
• Branch name: renovate/subsquid-evm-typegen-4.x-lockfile
• Merge into: master
• Upgrade @subsquid/evm-typegen to 4.6.0

Update dependency @​subsquid/graphql-server to v4.12.0

• Schedule: ["at any time"]
• Branch name: renovate/subsquid-graphql-server-4.x-lockfile
• Merge into: master
• Upgrade @subsquid/graphql-server to 4.12.0

Update dependency @​subsquid/logger to v1.6.0

• Schedule: ["at any time"]
• Branch name: renovate/subsquid-logger-1.x-lockfile
• Merge into: master
• Upgrade @subsquid/logger to 1.6.0

Update dependency @​subsquid/typeorm-codegen to v2.2.0

• Schedule: ["at any time"]
• Branch name: renovate/subsquid-typeorm-codegen-2.x-lockfile
• Merge into: master
• Upgrade @subsquid/typeorm-codegen to 2.2.0

Update dependency @​subsquid/typeorm-store to v1.9.1

• Schedule: ["at any time"]
• Branch name: renovate/subsquid-typeorm-store-1.x-lockfile
• Merge into: master
• Upgrade @subsquid/typeorm-store to 1.9.1

Update dependency @​types/node to v25.9.4

• Schedule: ["at any time"]
• Branch name: renovate/node-25.x-lockfile
• Merge into: master
• Upgrade @types/node to 25.9.4

Update dependency dotenv to v17.4.2

• Schedule: ["at any time"]
• Branch name: renovate/dotenv-17.x-lockfile
• Merge into: master
• Upgrade dotenv to 17.4.2

Update dependency pg to v8.22.0

• Schedule: ["at any time"]
• Branch name: renovate/pg-8.x-lockfile
• Merge into: master
• Upgrade pg to 8.22.0

Update dependency @​subsquid/batch-processor to v1

• Schedule: ["at any time"]
• Branch name: renovate/subsquid-batch-processor-1.x
• Merge into: master
• Upgrade @subsquid/batch-processor to ^1.0.0

Update dependency @​subsquid/evm-abi to v1

• Schedule: ["at any time"]
• Branch name: renovate/subsquid-evm-abi-1.x
• Merge into: master
• Upgrade @subsquid/evm-abi to ^1.0.0

Update dependency @​subsquid/evm-typegen to v5

• Schedule: ["at any time"]
• Branch name: renovate/subsquid-evm-typegen-5.x
• Merge into: master
• Upgrade @subsquid/evm-typegen to ^5.0.0

Update dependency typeorm to v1

• Schedule: ["at any time"]
• Branch name: renovate/typeorm-1.x
• Merge into: master
• Upgrade typeorm to ^1.0.0

Update dependency typescript to v6

• Schedule: ["at any time"]
• Branch name: renovate/typescript-6.x
• Merge into: master
• Upgrade typescript to ~6.0.0

Update postgres Docker tag to v18

• Schedule: ["at any time"]
• Branch name: renovate/postgres-18.x
• Merge into: master
• Upgrade postgres to 18

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