Skip to content

chore: Configure Renovate#95

Merged
designcode merged 2 commits intomainfrom
renovate/configure
May 9, 2026
Merged

chore: Configure Renovate#95
designcode merged 2 commits intomainfrom
renovate/configure

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 8, 2026

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

  • .devcontainer/devcontainer.json (devcontainer)
  • .devcontainer/Dockerfile (dockerfile)
  • .github/workflows/pr.yaml (github-actions)
  • .github/workflows/release.yaml (github-actions)
  • package.json (npm)
  • packages/agent-kit/package.json (npm)
  • packages/iam/package.json (npm)
  • packages/keyv-tigris/package.json (npm)
  • packages/react/package.json (npm)
  • packages/storage/package.json (npm)
  • pnpm-workspace.yaml (npm)
  • shared/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
  • Use semantic commit scope deps for all commits and PR titles.
  • Run lock file maintenance (updates) early Monday mornings.
  • Weekly schedule on early Monday mornings (before 4 AM).
  • Run Renovate on following schedule: * 0-3 * * 1

What to Expect

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

chore(deps): update dependency @​types/node to v20.19.40
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/node-20.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 20.19.40
chore(deps): update dependency publint to v0.3.20
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/publint-0.x-lockfile
  • Merge into: main
  • Upgrade publint to 0.3.20
chore(deps): update aws-sdk to v3.1045.0
chore(deps): update commitlint to v21 (major)
chore(deps): update dependency @​types/node to v24
  • Schedule: ["every 2 weeks on monday before 6am"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade @types/node to ^24.0.0
chore(deps): update dependency typescript to v6
  • Schedule: ["every 2 weeks on monday before 6am"]
  • Branch name: renovate/typescript-6.x
  • Merge into: main
  • Upgrade typescript to ^6.0.0
chore(deps): update ghcr.io/devcontainers/features/node docker tag to v2
  • Schedule: ["every 2 weeks on monday before 6am"]
  • Branch name: renovate/ghcr.io-devcontainers-features-node-2.x
  • Merge into: main
  • Upgrade ghcr.io/devcontainers/features/node to 2
chore(deps): update github-actions to v6 (major)
chore(deps): update pnpm to v11
  • Schedule: ["every 2 weeks on monday before 6am"]
  • Branch name: renovate/major-pnpm
  • Merge into: main
  • Upgrade pnpm to 11.0.9
chore(deps): lock file maintenance
  • Schedule: ["before 6am on monday"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: main
  • Regenerate lock files to use latest dependency versions

🚸 PR creation will be limited to maximum 4 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.

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 8, 2026

Greptile Summary

This PR onboards Renovate by adding a minimal renovate.json config file that extends the config:recommended preset. Merging activates automated dependency update PRs across the detected package files.

  • Adds renovate.json with only the config:recommended preset — no custom scheduling, grouping, or automerge rules.
  • Renovate will begin opening up to 10 dependency update PRs once merged, rate-limited to 2 per hour.

Confidence Score: 5/5

Safe to merge — adds only a minimal Renovate config file with no logic changes.

The change is a single new JSON file with six lines, delegating all behavior to Renovate's well-maintained recommended preset. Nothing in the codebase is modified, and the bot will not act until this PR is merged.

No files require special attention.

Important Files Changed

Filename Overview
renovate.json Adds a minimal Renovate onboarding config that extends the recommended preset with no custom overrides.

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

renovate Bot and others added 2 commits May 9, 2026 15:38
Renovate config:
- Group related ecosystems so we get one PR per ecosystem instead of
  per package: aws-sdk (sdk + crypto + smithy), changesets, commitlint,
  biome, react (peer + test deps), keyv, github-actions, pnpm.
- Auto-merge devDependency patches/minors, GitHub Actions patches/minors,
  and weekly lockfile maintenance.
- Schedule weekly with prHourlyLimit=4 and prConcurrentLimit=10; security
  alerts override the schedule.
- Throttle major-version updates to every two weeks so we batch them
  instead of getting one every Monday.
- Run weekly lockfile maintenance Mondays before 6am; pnpmDedupe after
  every update.
- Use semantic commit scope `deps` (matches our commitlint scope rule).

Workflow tweaks:
- Drop the explicit `version: 10.33.4` from pnpm/action-setup in pr.yaml
  and release.yaml. The action reads `package.json#packageManager`
  automatically, so the pnpm version now lives in exactly one place.
- Drop the changeset gate from pr.yaml. The gate's purpose was to force
  every package change to declare its own release; we'll rely on PR
  review to ensure changesets are added when needed instead. This also
  removes the need for a Renovate-PR auto-changeset workflow.

Assisted-by: Claude Opus 4.7 (1M context) via Claude Code

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@designcode designcode force-pushed the renovate/configure branch from b36d483 to 8a95300 Compare May 9, 2026 14:05
@designcode designcode changed the title chore: Configure Renovate chore: configure renovate May 9, 2026
@renovate renovate Bot changed the title chore: configure renovate chore: Configure Renovate May 9, 2026
@designcode designcode merged commit d2c2ca0 into main May 9, 2026
1 check passed
@designcode designcode deleted the renovate/configure branch May 9, 2026 14:09
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