Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Oct 28, 2025

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.


Detected Package Files

  • .github/workflows/bench.yml (github-actions)
  • .github/workflows/deploy-definer-zephyr.yml (github-actions)
  • .github/workflows/deploy-frontend.yml (github-actions)
  • .github/workflows/deploy-worker-dev.yml (github-actions)
  • .github/workflows/deploy-worker-release.yml (github-actions)
  • apps/benchmark-report/package.json (npm)
  • apps/definer/package.json (npm)
  • apps/worker/package.json (npm)
  • package.json (npm)
  • packages/agency-prompt-creator/package.json (npm)
  • packages/agent-adapters/package.json (npm)
  • packages/evaluators/package.json (npm)
  • packages/harness/package.json (npm)
  • packages/logger/package.json (npm)
  • packages/specialist-mint/package.json (npm)
  • packages/specialist-mint/pnpm-workspace.yaml (npm)
  • packages/worker-client/package.json (npm)
  • pnpm-workspace.yaml (npm)
  • suites/next.js/scenarios/000-app-router-migration-simple/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/001-server-component/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/002-client-component/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/003-cookies/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/004-search-params/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/005-react-use-api/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/006-server-metadata/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/007-client-metadata/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/008-generate-static-params/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/009-og-images/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/010-route-handlers/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/011-client-server-form/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/012-parallel-routes/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/013-pathname-server/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/014-server-routing/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/015-server-actions-exports/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/016-client-cookies/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/017-use-search-params/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/018-use-router/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/019-use-action-state/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/020-no-use-effect/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/021-avoid-fetch-in-effect/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/022-prefer-server-actions/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/023-avoid-getserversideprops/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/024-avoid-redundant-usestate/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/025-prefer-next-link/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/026-no-serial-await/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/027-prefer-next-image/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/028-prefer-next-font/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/029-use-cache-directive/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/030-app-router-migration-hard/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/031-ai-sdk-migration-simple/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/032-ai-sdk-model-specification-string/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/033-ai-sdk-v4-model-specification-function/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/034-ai-sdk-render-visual-info/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/035-ai-sdk-call-tools/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/036-ai-sdk-call-tools-multiple-steps/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/037-ai-sdk-embed-text/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/038-ai-sdk-mcp/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/039-parallel-routes/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/040-intercepting-routes/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/041-route-groups/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/042-loading-ui/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/043-error-boundaries/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/044-metadata-api/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/045-server-actions-form/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/046-streaming/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/047-middleware/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/048-draft-mode/repo-fixture/package.json (npm)
  • suites/next.js/scenarios/049-revalidation/repo-fixture/package.json (npm)
  • suites/test-suite/scenarios/test-scenario/repo-fixture/apps/app/package.json (npm)
  • suites/test-suite/scenarios/test-scenario/repo-fixture/libs/util/package.json (npm)
  • suites/test-suite/scenarios/test-scenario/repo-fixture/package.json (npm)
  • suites/test-suite/scenarios/test-scenario/repo-fixture/pnpm-workspace.yaml (npm)
  • suites/update-deps/scenarios/nx-pnpm-monorepo/repo-fixture/apps/app/package.json (npm)
  • suites/update-deps/scenarios/nx-pnpm-monorepo/repo-fixture/libs/util/package.json (npm)
  • suites/update-deps/scenarios/nx-pnpm-monorepo/repo-fixture/package.json (npm)
  • suites/update-deps/scenarios/nx-pnpm-monorepo/repo-fixture/pnpm-workspace.yaml (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 GitHub.com contains a link to the commit-to-commit diff
  • Weekly schedule on early Monday mornings (before 4 AM).
  • Group all minor and patch updates together.
  • Apply label dependencies to PRs.
  • Automerge patch and minor upgrades if they pass tests.
  • Do not update peerDependencies versions/ranges.
  • Enable Renovate Dependency Dashboard creation.
  • Run Renovate on following schedule: * 0-3 * * 1

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


What to Expect

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

fix(deps): update all non-major dependencies
chore(deps): update actions/checkout action to v6
  • Schedule: ["* 0-3 * * 1"]
  • 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: ["* 0-3 * * 1"]
  • Branch name: renovate/actions-setup-node-6.x
  • Merge into: main
  • Upgrade actions/setup-node to v6
chore(deps): update actions/upload-artifact action to v5
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/major-github-artifact-actions
  • Merge into: main
  • Upgrade actions/upload-artifact to v5
chore(deps): update dependency @​types/node to v24
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade @types/node to ^24.0.0
chore(deps): update dependency nx to v22
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/major-nx-monorepo
  • Merge into: main
  • Upgrade nx to ~22.2.0
chore(deps): update dependency ubuntu to v24
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/ubuntu-24.x
  • Merge into: main
  • Upgrade ubuntu to 24.04
chore(deps): update pnpm to v10
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/pnpm-10.x
  • Merge into: main
  • Upgrade pnpm to 10.25.0
  • Upgrade pnpm to 10
fix(deps): update dependency @​vitejs/plugin-react to v5
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/vitejs-plugin-react-5.x
  • Merge into: main
  • Upgrade @vitejs/plugin-react to ^5.0.0
fix(deps): update dependency ai to v5
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/ai-5.x
  • Merge into: main
  • Upgrade ai to 5.0.108
fix(deps): update dependency dotenv to v17
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/dotenv-17.x
  • Merge into: main
  • Upgrade dotenv to ^17.0.0
fix(deps): update dependency globby to v16
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/globby-16.x
  • Merge into: main
  • Upgrade globby to ^16.0.0
fix(deps): update dependency itty-router to v5
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/itty-router-5.x
  • Merge into: main
  • Upgrade itty-router to ^5.0.0
fix(deps): update dependency jsdom to v27
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/jsdom-27.x
  • Merge into: main
  • Upgrade jsdom to ^27.0.0
fix(deps): update dependency openai to v6
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/openai-6.x
  • Merge into: main
  • Upgrade openai to ^6.0.0
fix(deps): update dependency recharts to v3
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/recharts-3.x
  • Merge into: main
  • Upgrade recharts to 3.5.1
fix(deps): update dependency vitest to v4
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/major-vitest-monorepo
  • Merge into: main
  • Upgrade vitest to ^4.0.0
fix(deps): update nextjs monorepo to v16 (major)
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/major-nextjs-monorepo
  • Merge into: main
  • Upgrade eslint-config-next to 16.0.8
  • Upgrade next to 16.0.8
fix(deps): update react monorepo to v19 (major)

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

@renovate renovate bot force-pushed the renovate/configure branch from 6a36010 to 1f47ace Compare December 10, 2025 07:13
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