Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Aug 5, 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

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

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

chore(deps): update dependency typedoc to ^0.28.0
  • Schedule: ["at any time"]
  • Branch name: renovate/typedoc-0.x
  • Merge into: main
  • Upgrade typedoc to ^0.28.0
chore(deps): update dependency @​types/uuid to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/uuid-10.x
  • Merge into: main
  • Upgrade @types/uuid to ^10.0.0
chore(deps): update dependency @​types/wicg-file-system-access to v2023
chore(deps): update dependency eslint to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/major-eslint-monorepo
  • Merge into: main
  • Upgrade eslint to ^9.0.0
chore(deps): update dependency mocha to v11
  • Schedule: ["at any time"]
  • Branch name: renovate/mocha-11.x
  • Merge into: main
  • Upgrade mocha to ^11.0.0
chore(deps): update dependency typedoc-plugin-markdown to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/typedoc-plugin-markdown-4.x
  • Merge into: main
  • Upgrade typedoc-plugin-markdown to ^4.0.0
chore(deps): update dependency typescript to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-5.x
  • Merge into: main
  • Upgrade typescript to ^5.0.0
chore(deps): update dependency webpack-cli to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/webpack-cli-6.x
  • Merge into: main
  • Upgrade webpack-cli to ^6.0.0
chore(deps): update typescript-eslint monorepo to v8 (major)
fix(deps): update dependency uuid to v11
  • Schedule: ["at any time"]
  • Branch name: renovate/uuid-11.x
  • Merge into: main
  • Upgrade uuid to ^11.0.0
fix(deps): update dependency workbox-streams to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/major-workbox-monorepo
  • Merge into: main
  • Upgrade workbox-streams to ^7.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.


Warning

Please correct - or verify that you can safely ignore - these dependency lookup failures before you merge this PR.

  • Could not determine new digest for update (github-tags package Sec-ant/jsSHA)

Files affected: package.json


❓ 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 Aug 5, 2025

⚠️ No Changeset found

Latest commit: 4ae7898

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.

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

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