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/actions/setup/action.yml (github-actions)
  • .github/workflows/build-deploy-test.yml (github-actions)
  • scripts/package.json (npm)
  • vanilla/package.json (npm)
  • vanilla/pnpm-workspace.yaml (npm)
  • .nvmrc (nvm)

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

🔡 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 7 Pull Requests:

chore(deps): update dependency @​playwright/test to v1.57.0
  • Schedule: ["at any time"]
  • Branch name: renovate/playwright-monorepo
  • Merge into: main
  • Upgrade @playwright/test to 1.57.0
chore(deps): update dependency tsx to v4.21.0
  • Schedule: ["at any time"]
  • Branch name: renovate/tsx-4.x-lockfile
  • Merge into: main
  • Upgrade tsx to 4.21.0
chore(deps): update pnpm to v10.24.0
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-10.x
  • Merge into: main
  • Upgrade pnpm to 10.24.0
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 actions/upload-artifact action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/major-github-artifact-actions
  • Merge into: main
  • Upgrade actions/upload-artifact to v5
fix(deps): update dependency @​types/node to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade @types/node to ^24.0.0

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

@cla-assistant
Copy link

cla-assistant bot commented Oct 28, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Nsttt
❌ renovate[bot]
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.

2 participants