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

• package.json (npm)
• tasks/icebreaker/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.

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

chore(deps): update dependency @​types/parse-git-config to v3.0.4

• Schedule: ["at any time"]
• Branch name: renovate/parse-git-config-3.x-lockfile
• Merge into: main
• Upgrade @types/parse-git-config to 3.0.4

chore(deps): update dependency mrm to v4.1.22

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

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

fix(deps): update dependency mrm-core to v7.1.22

• Schedule: ["at any time"]
• Branch name: renovate/mrm-core-7.x-lockfile
• Merge into: main
• Upgrade mrm-core to 7.1.22

chore(deps): update dependency @​icebreakers/rollup to ^0.4.0

• Schedule: ["at any time"]
• Branch name: renovate/icebreakers-rollup-0.x
• Merge into: main
• Upgrade @icebreakers/rollup to ^0.4.0

chore(deps): update dependency eslint to v8.57.1

• Schedule: ["at any time"]
• Branch name: renovate/eslint-monorepo
• Merge into: main
• Upgrade eslint to 8.57.1

chore(deps): update dependency rollup to v3.29.5

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

chore(deps): update dependency tslib to v2.8.0

• Schedule: ["at any time"]
• Branch name: renovate/tslib-2.x-lockfile
• Merge into: main
• Upgrade tslib to 2.8.0

chore(deps): update pnpm to v7.33.7

• Schedule: ["at any time"]
• Branch name: renovate/pnpm-7.x
• Merge into: main
• Upgrade pnpm to 7.33.7

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 rollup to v4

• Schedule: ["at any time"]
• Branch name: renovate/rollup-4.x
• Merge into: main
• Upgrade rollup 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 pnpm to v9

• Schedule: ["at any time"]
• Branch name: renovate/pnpm-9.x
• Merge into: main
• Upgrade pnpm to 9.12.1

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: b59cf29

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