Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Nov 1, 2023

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/build.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:

Replace dependency rollup-plugin-node-resolve with @​rollup/plugin-node-resolve ^6.0.0
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-node-resolve-replacement
  • Merge into: main
  • Upgrade rollup-plugin-node-resolve to ^6.0.0
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
Update actions/setup-node action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-4.x
  • Merge into: main
  • Upgrade actions/setup-node to v4
Update dependency @​rollup/plugin-replace to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-replace-5.x
  • Merge into: main
  • Upgrade @rollup/plugin-replace to ^5.0.0
Update dependency @​tensorflow/tfjs to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/tensorflow-tfjs-4.x
  • Merge into: main
  • Upgrade @tensorflow/tfjs to ^4.0.0
Update dependency rollup to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-4.x
  • Merge into: main
  • Upgrade rollup to ^4.0.0
Update dependency rollup-plugin-livereload to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-livereload-2.x
  • Merge into: main
  • Upgrade rollup-plugin-livereload to ^2.0.0
Update dependency rollup-plugin-svelte to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-svelte-7.x
  • Merge into: main
  • Upgrade rollup-plugin-svelte to ~7.1.0
Update dependency rollup-plugin-terser to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-terser-7.x
  • Merge into: main
  • Upgrade rollup-plugin-terser to ^7.0.0
Update dependency sirv-cli to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/sirv-cli-2.x
  • Merge into: main
  • Upgrade sirv-cli to ^2.0.0
Update dependency svelte to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/svelte-4.x
  • Merge into: main
  • Upgrade svelte 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/configure branch from deb28fa to a49bf46 Compare December 15, 2023 05:38
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