Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Configure Renovate #2

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: Configure Renovate #2

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 14, 2024

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
  • 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.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Wait until the npm package is three days old before raising the update, this prevents npm unpublishing a package you already upgraded to.
  • Weekly schedule on early Monday mornings (before 4 AM).
  • Disable automerging feature - wait for humans to merge all PRs.
  • Enable Renovate Dependency Dashboard creation.
  • Append Signed-off-by: to signoff Git commits.
  • Rebase existing PRs any time the base branch has been updated.
  • Default Renovate configuration for celo-org. Docs at https://docs.renovatebot.com/.
  • Run Renovate on following schedule: * 0-3 * * 1

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

chore(deps): update dependency @​sveltejs/vite-plugin-svelte to v5.0.2
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/sveltejs-vite-plugin-svelte-5.x
  • Merge into: main
  • Upgrade @sveltejs/vite-plugin-svelte to 5.0.2
chore(deps): update dependency @​types/node to v22.10.2
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/node-22.x
  • Merge into: main
  • Upgrade @types/node to 22.10.2
chore(deps): update dependency eslint-plugin-svelte to v2.46.1
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/eslint-plugin-svelte-2.x-lockfile
  • Merge into: main
  • Upgrade eslint-plugin-svelte to 2.46.1
chore(deps): update dependency prettier to v3.4.2
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/prettier-3.x-lockfile
  • Merge into: main
  • Upgrade prettier to 3.4.2
chore(deps): update dependency svelte-check to v4.1.1
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/svelte-check-4.x
  • Merge into: main
  • Upgrade svelte-check to 4.1.1
chore(deps): update dependency tailwindcss to v3.4.16
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/tailwindcss-3.x
  • Merge into: main
  • Upgrade tailwindcss to 3.4.16
chore(deps): update dependency vite to v6.0.3
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/vite-6.x-lockfile
  • Merge into: main
  • Upgrade vite to 6.0.3
chore(deps): update dependency vitest to v2.1.8
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/vitest-monorepo
  • Merge into: main
  • Upgrade vitest to 2.1.8
fix(deps): update dependency @​wagmi/connectors to v5.5.3
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/wagmi-connectors-5.x
  • Merge into: main
  • Upgrade @wagmi/connectors to 5.5.3
fix(deps): update dependency @​wagmi/core to v2.15.2
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/wagmi-core-2.x-lockfile
  • Merge into: main
  • Upgrade @wagmi/core to 2.15.2
fix(deps): update dependency viem to v2.21.54
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/viem-2.x
  • Merge into: main
  • Upgrade viem to 2.21.54
chore(deps): update dependency @​sveltejs/kit to v2.10.1
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/sveltejs-kit-2.x-lockfile
  • Merge into: main
  • Upgrade @sveltejs/kit to 2.10.1
chore(deps): update dependency eslint to v9.16.0
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/eslint-monorepo
  • Merge into: main
  • Upgrade eslint to 9.16.0
chore(deps): update dependency svelte to v5.10.1
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/svelte-5.x
  • Merge into: main
  • Upgrade svelte to 5.10.1
chore(deps): update dependency typescript to v5.7.2
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/typescript-5.x
  • Merge into: main
  • Upgrade typescript to 5.7.2
chore(deps): update dependency vite-plugin-tailwind-purgecss to v0.3.5
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/vite-plugin-tailwind-purgecss-0.x
  • Merge into: main
  • Upgrade vite-plugin-tailwind-purgecss to 0.3.5
chore(deps): update typescript-eslint monorepo to v8.18.0
fix(deps): update dependency @​tanstack/react-query to v5.62.7
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/tanstack-query-monorepo
  • Merge into: main
  • Upgrade @tanstack/react-query to 5.62.7

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

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
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