Configure Renovate

[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

• Dockerfile.gitpod (dockerfile)
• .github/workflows/publish.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 21 Pull Requests:

chore(deps): update dependency eslint-plugin-react-refresh to v0.4.8

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-react-refresh-0.x-lockfile
• Merge into: main
• Upgrade eslint-plugin-react-refresh to 0.4.8

chore(deps): update dependency nodemon to v3.1.4

• Schedule: ["at any time"]
• Branch name: renovate/nodemon-3.x-lockfile
• Merge into: main
• Upgrade nodemon to 3.1.4

chore(deps): update dependency vite to v4.5.3

• Schedule: ["at any time"]
• Branch name: renovate/vite-4.x-lockfile
• Merge into: main
• Upgrade vite to 4.5.3

chore(deps): update dependency @​vitejs/plugin-react-swc to v3.7.0

• Schedule: ["at any time"]
• Branch name: renovate/vitejs-plugin-react-swc-3.x-lockfile
• Merge into: main
• Upgrade @vitejs/plugin-react-swc to 3.7.0

chore(deps): update dependency electron to v28.3.3

• Schedule: ["at any time"]
• Branch name: renovate/electron-28.x-lockfile
• Merge into: main
• Upgrade electron to 28.3.3

chore(deps): update dependency typescript to v5.5.3

• Schedule: ["at any time"]
• Branch name: renovate/typescript-5.x-lockfile
• Merge into: main
• Upgrade typescript to 5.5.3

chore(deps): update react monorepo

• Schedule: ["at any time"]
• Branch name: renovate/react-monorepo
• Merge into: main
• Upgrade @types/react to 18.3.3
• Upgrade @types/react-dom to 18.3.0
• Upgrade eslint-plugin-react-hooks to 4.6.2
• Upgrade react to 18.3.1
• Upgrade react-dom to 18.3.1

chore(deps): update swc monorepo

• Schedule: ["at any time"]
• Branch name: renovate/swc-monorepo
• Merge into: main
• Upgrade @swc/cli to ^0.4.0
• Upgrade @swc/core to 1.7.0

fix(deps): update dependency i18next to v23.12.2

• Schedule: ["at any time"]
• Branch name: renovate/i18next-23.x-lockfile
• Merge into: main
• Upgrade i18next to 23.12.2

fix(deps): update emotion monorepo to v11.13.0

• Schedule: ["at any time"]
• Branch name: renovate/emotion-monorepo
• Merge into: main
• Upgrade @emotion/react to 11.13.0
• Upgrade @emotion/styled to 11.13.0

fix(deps): update font awesome

• Schedule: ["at any time"]
• Branch name: renovate/font-awesome
• Merge into: main
• Upgrade @fortawesome/fontawesome-svg-core to 6.6.0
• Upgrade @fortawesome/free-brands-svg-icons to 6.6.0
• Upgrade @fortawesome/free-solid-svg-icons to 6.6.0
• Upgrade @fortawesome/react-fontawesome to 0.2.2

fix(deps): update material-ui monorepo to v5.16.4

• Schedule: ["at any time"]
• Branch name: renovate/material-ui-monorepo
• Merge into: main
• Upgrade @mui/icons-material to 5.16.4
• Upgrade @mui/material to 5.16.4

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

chore(deps): update actions/upload-artifact action to v4

• Schedule: ["at any time"]
• Branch name: renovate/major-github-artifact-actions
• Merge into: main
• Upgrade actions/upload-artifact to v4

chore(deps): update dependency electron to v31

• Schedule: ["at any time"]
• Branch name: renovate/electron-31.x
• Merge into: main
• Upgrade electron to ^31.0.0

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 vite to v5

• Schedule: ["at any time"]
• Branch name: renovate/vite-5.x
• Merge into: main
• Upgrade vite to ^5.0.0

chore(deps): update typescript-eslint monorepo to v7 (major)

• Schedule: ["at any time"]
• Branch name: renovate/major-typescript-eslint-monorepo
• Merge into: main
• Upgrade @typescript-eslint/eslint-plugin to ^7.0.0
• Upgrade @typescript-eslint/parser to ^7.0.0

fix(deps): update dependency react-i18next to v15

• Schedule: ["at any time"]
• Branch name: renovate/react-i18next-15.x
• Merge into: main
• Upgrade react-i18next to ^15.0.0

fix(deps): update dependency react-snowfall to v2

• Schedule: ["at any time"]
• Branch name: renovate/react-snowfall-2.x
• Merge into: main
• Upgrade react-snowfall to ^2.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.

[SrIzan10]

@jacoobes should I? dependabot have always worked fine for me...

[jacoobes]

Leave this open

…

On Sat, Jun 10, 2023 at 6:30 AM SrIzan10 ***@***.***> wrote: @jacoobes <https://github.com/jacoobes> should I? dependabot have always worked fine for me... — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASJS6O4RQRI5COTCQV33D33XKRLEFANCNFSM6AAAAAAY2DAWXE> . You are receiving this because you were mentioned.Message ID: ***@***.***>