Skip to content

chore: Configure Renovate#196

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

chore: Configure Renovate#196
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure

Conversation

@renovate
Copy link

@renovate renovate bot commented Feb 17, 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.


Detected Package Files

  • .github/workflows/ci.yml (github-actions)
  • .github/workflows/release.yml (github-actions)
  • package.json (npm)
  • packages/eslint-config/package.json (npm)
  • packages/gear/package.json (npm)
  • packages/typescript-config/package.json (npm)
  • packages/vitest-config/package.json (npm)
  • packages/wz-gear/package.json (npm)
  • 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
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title

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

chore(deps): update dependency glob to v11.1.0 [security]
  • Branch name: renovate/npm-glob-vulnerability
  • Merge into: main
  • Upgrade glob to 11.1.0
chore(deps): update dependency @​changesets/cli to v2.29.8
  • Schedule: ["at any time"]
  • Branch name: renovate/changesets-cli-2.x-lockfile
  • Merge into: main
  • Upgrade @changesets/cli to 2.29.8
chore(deps): update dependency eslint-config-prettier to v10.1.8
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-config-prettier-10.x-lockfile
  • Merge into: main
  • Upgrade eslint-config-prettier to 10.1.8
chore(deps): update pnpm to v9.15.9
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-9.x
  • Merge into: main
  • Upgrade pnpm to 9.15.9
chore(deps): update dependency @​microsoft/api-extractor to v7.57.1
  • Schedule: ["at any time"]
  • Branch name: renovate/microsoft-api-extractor-7.x-lockfile
  • Merge into: main
  • Upgrade @microsoft/api-extractor to 7.57.1
chore(deps): update dependency @​types/node to v22.19.11
  • Schedule: ["at any time"]
  • Branch name: renovate/node-22.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 22.19.11
chore(deps): update dependency prettier to v3.8.1
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x-lockfile
  • Merge into: main
  • Upgrade prettier to 3.8.1
chore(deps): update dependency tsup to v8.5.1
  • Schedule: ["at any time"]
  • Branch name: renovate/tsup-8.x-lockfile
  • Merge into: main
  • Upgrade tsup to 8.5.1
chore(deps): update dependency typescript to v5.9.3
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-5.x-lockfile
  • Merge into: main
  • Upgrade typescript to 5.9.3
chore(deps): update dependency typescript-eslint to v8.56.0
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-eslint-monorepo
  • Merge into: main
  • Upgrade typescript-eslint to 8.56.0
chore(deps): update eslint monorepo to v9.39.2
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: main
  • Upgrade @eslint/js to 9.39.2
  • Upgrade eslint to 9.39.2
chore(deps): update turbo monorepo to v2.8.10
  • Schedule: ["at any time"]
  • Branch name: renovate/turbo-monorepo
  • Merge into: main
  • Upgrade eslint-plugin-turbo to 2.8.10
  • Upgrade turbo to 2.8.10
chore(deps): update vitest monorepo to v3.2.4
chore(deps): update actions/cache action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-cache-5.x
  • Merge into: main
  • Upgrade actions/cache to v5
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 dependency globals to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/globals-17.x
  • Merge into: main
  • Upgrade globals to ^17.0.0
chore(deps): update dependency node to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade node to 24.x
  • Upgrade @types/node to ^24.0.0
chore(deps): update eslint monorepo to v10 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: main
  • Upgrade @eslint/js to ^10.0.0
  • Upgrade eslint to ^10.0.0
chore(deps): update pnpm to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-10.x
  • Merge into: main
  • Upgrade pnpm to 10.30.1
chore(deps): update pnpm/action-setup action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-action-setup-4.x
  • Merge into: main
  • Upgrade pnpm/action-setup to v4
chore(deps): update vitest monorepo to v4 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-vitest-monorepo
  • Merge into: main
  • Upgrade @vitest/coverage-istanbul to ^4.0.0
  • Upgrade vitest to ^4.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.

@changeset-bot
Copy link

changeset-bot bot commented Feb 17, 2026

⚠️ No Changeset found

Latest commit: 2180a8e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@cloudflare-workers-and-pages
Copy link

Deploying malib-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 2180a8e
Status:🚫  Build failed.

View logs

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.

0 participants