Skip to content

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 6, 2021

Mend Renovate

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/docs.yml (github-actions)
  • package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • 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 directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • 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 nodemon to v2.0.22
  • Schedule: ["at any time"]
  • Branch name: renovate/nodemon-2.x-lockfile
  • Merge into: main
  • Upgrade nodemon to 2.0.22
chore(deps): update dependency @​types/node to v16.18.68
  • Schedule: ["at any time"]
  • Branch name: renovate/node-16.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 16.18.68
chore(deps): update dependency prettier to v2.8.8
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-2.x-lockfile
  • Merge into: main
  • Upgrade prettier to 2.8.8
chore(deps): update dependency ts-node to v10.9.2
  • Schedule: ["at any time"]
  • Branch name: renovate/ts-node-10.x-lockfile
  • Merge into: main
  • Upgrade ts-node to 10.9.2
chore(deps): update dependency typedoc to ^0.25.0
  • Schedule: ["at any time"]
  • Branch name: renovate/typedoc-0.x
  • Merge into: main
  • Upgrade typedoc to ^0.25.0
chore(deps): update dependency typescript to v4.9.5
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-4.x-lockfile
  • Merge into: main
  • Upgrade typescript to 4.9.5
chore(deps): update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • Upgrade actions/checkout to v4
chore(deps): update dependency @​types/node to v20
  • Schedule: ["at any time"]
  • Branch name: renovate/node-20.x
  • Merge into: main
  • Upgrade @types/node to ^20.0.0
chore(deps): update dependency nodemon to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/nodemon-3.x
  • Merge into: main
  • Upgrade nodemon to ^3.0.0
chore(deps): update dependency prettier to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x
  • Merge into: main
  • Upgrade prettier to ^3.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

🚸 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/configure branch from 6798e78 to 4aa8209 Compare June 26, 2022 08:52
@renovate renovate bot force-pushed the renovate/configure branch from 4aa8209 to f03d1b1 Compare December 15, 2023 17:50
Copy link

changeset-bot bot commented Dec 15, 2023

⚠️ No Changeset found

Latest commit: f03d1b1

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.

0 participants