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

• .devcontainer.json (devcontainer)
• .github/workflows/ci.yml (github-actions)
• .github/workflows/dependency-review.yml (github-actions)
• .github/workflows/pkg.pr.new.yml (github-actions)
• .github/workflows/release.yml (github-actions)
• .github/workflows/variables.yml (github-actions)
• docs/package.json (npm)
• libraries/ui-library-angular/package.json (npm)
• libraries/ui-library-react/package.json (npm)
• libraries/ui-library-vue/package.json (npm)
• libraries/ui-library/package.json (npm)
• package.json (npm)

Configuration Summary

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

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• 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.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Ensure that every dependency pinned by digest and sourced from GitHub.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title

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

---

You have configured Renovate to use branch main as base branch.

What to Expect

With your current configuration, Renovate will create 15 Pull Requests:

chore(deps): update actions/checkout action to v5.0.1

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-5.x
• Merge into: main
• Upgrade actions/checkout to 93cb6efe18208431cddfb8368fd83d5badbf9bfd

chore(deps): update dependency pkg-pr-new to ^0.0.65

• Schedule: ["at any time"]
• Branch name: renovate/pkg-pr-new-0.x
• Merge into: main
• Upgrade pkg-pr-new to ^0.0.65

chore(deps): update dependency @​docsearch/css to v3.9.0

• Schedule: ["at any time"]
• Branch name: renovate/docsearch-css-3.x-lockfile
• Merge into: main
• Upgrade @docsearch/css to 3.9.0

chore(deps): update dependency @​docsearch/js to v3.9.0

• Schedule: ["at any time"]
• Branch name: renovate/docsearch-js-3.x-lockfile
• Merge into: main
• Upgrade @docsearch/js to 3.9.0

chore(deps): update dependency @​stencil/angular-output-target to v1.3.0

• Schedule: ["at any time"]
• Branch name: renovate/stencil-angular-output-target-1.x
• Merge into: main
• Upgrade @stencil/angular-output-target to 1.3.0

chore(deps): update dependency @​stencil/vue-output-target to v0.13.1

• Schedule: ["at any time"]
• Branch name: renovate/stencil-vue-output-target-0.x
• Merge into: main
• Upgrade @stencil/vue-output-target to 0.13.1

fix(deps): update dependency @​stencil/core to v4.43.2

• Schedule: ["at any time"]
• Branch name: renovate/stencil-core-4.x
• Merge into: main
• Upgrade @stencil/core to 4.43.2

chore(deps): update actions/checkout action to v6

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-6.x
• Merge into: main
• Upgrade actions/checkout to v6
• Upgrade actions/checkout to de0fac2e4500dabe0009e67214ff5f5447ce83dd

chore(deps): update actions/setup-node action to v6

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-node-6.x
• Merge into: main
• Upgrade actions/setup-node to v6

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

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

chore(deps): update dependency @​docsearch/css to v4

• Schedule: ["at any time"]
• Branch name: renovate/docsearch-css-4.x
• Merge into: main
• Upgrade @docsearch/css to 4.6.0

chore(deps): update dependency @​docsearch/js to v4

• Schedule: ["at any time"]
• Branch name: renovate/docsearch-js-4.x
• Merge into: main
• Upgrade @docsearch/js to 4.6.0

chore(deps): update dependency eslint to v10

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

chore(deps): update jest monorepo to v30 (major)

• Schedule: ["at any time"]
• Branch name: renovate/major-jest-monorepo
• Merge into: main
• Upgrade @types/jest to ^30.0.0
• Upgrade jest to ^30.0.0
• Upgrade jest-cli to ^30.0.0

chore(deps): update mcr.microsoft.com/devcontainers/typescript-node docker tag to v1

• Schedule: ["at any time"]
• Branch name: renovate/mcr.microsoft.com-devcontainers-typescript-node-1.x
• Merge into: main
• Upgrade mcr.microsoft.com/devcontainers/typescript-node to 1-18

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

[renovate]

Branch Conflicted

⚠️ This PR has a merge conflict which Renovate is unable to automatically resolve, so updates to this PR description are now paused. Please resolve the merge conflict manually.

[github-actions]

File	Coverage
All files	92%	✅
www/build/src/components/six-breadcrumbs/six-breadcrumbs.tsx	90%	✅
www/build/src/components/six-button/six-button.tsx	91%	✅
www/build/src/components/six-checkbox/six-checkbox.tsx	93%	✅
www/build/src/components/six-date/calendar-grid.ts	93%	✅
www/build/src/components/six-date/six-date.tsx	96%	✅
www/build/src/components/six-date/components/month-selection.tsx	90%	✅
www/build/src/components/six-date/components/year-selection.tsx	91%	✅
www/build/src/components/six-details/six-details.tsx	98%	✅
www/build/src/components/six-dialog/six-dialog.tsx	98%	✅
www/build/src/components/six-dropdown/six-dropdown.tsx	94%	✅
www/build/src/components/six-error-page/six-error-page.tsx	90%	✅
www/build/src/components/six-file-upload/six-file-upload.tsx	95%	✅
www/build/src/components/six-group-label/six-group-label.tsx	83%	✅
www/build/src/components/six-icon/six-icon.tsx	62%	✅
www/build/src/components/six-icon-button/six-icon-button.tsx	90%	✅
www/build/src/components/six-input/six-input.tsx	97%	✅
www/build/src/components/six-item-picker/six-item-picker.tsx	99%	✅
www/build/src/components/six-menu/six-menu.tsx	80%	✅
www/build/src/components/six-menu-item/six-menu-item.tsx	99%	✅
www/build/src/components/six-picto/six-picto.tsx	66%	✅
www/build/src/components/six-progress-ring/six-progress-ring.tsx	75%	✅
www/build/src/components/six-range/six-range.tsx	92%	✅
www/build/src/components/six-rating/six-rating.tsx	96%	✅
www/build/src/components/six-search-field/six-search-field.tsx	90%	✅
www/build/src/components/six-select/six-select.tsx	88%	✅
www/build/src/components/six-select/util.ts	75%	✅
www/build/src/components/six-sidebar/six-sidebar.tsx	92%	✅
www/build/src/components/six-sidebar-item-group/six-sidebar-item-group.tsx	95%	✅
www/build/src/components/six-switch/six-switch.tsx	95%	✅
www/build/src/components/six-tab/six-tab.tsx	91%	✅
www/build/src/components/six-tab-group/six-tab-group.tsx	78%	✅
www/build/src/components/six-textarea/six-textarea.tsx	87%	✅
www/build/src/components/six-tile/six-tile.tsx	83%	✅
www/build/src/components/six-tooltip/six-tooltip.tsx	94%	✅
www/build/src/functional-components/form-control/form-control.tsx	89%	✅
www/build/src/utils/animation.ts	88%	✅
www/build/src/utils/error-messages.ts	84%	✅
www/build/src/utils/event-listeners.ts	91%	✅
www/build/src/utils/execution-control.ts	90%	✅
www/build/src/utils/focus-visible.ts	83%	✅
www/build/src/utils/icon.ts	92%	✅
www/build/src/utils/modal.ts	75%	✅
www/build/src/utils/popover.ts	83%	✅
www/build/src/utils/scroll.ts	87%	✅
www/build/src/utils/slot.ts	90%	✅

Minimum allowed coverage is 0%

Generated by 🐒 cobertura-action against 610f971

[pennal]

To me, this looks good, but I do not fully understand how it works.

Will it simply open up PRs for the new dependencies? Is it possible to tell it to avoid major upgrades?

Also might be worth rebasing since the package-lock.json has changed a bit @colinscz

I will approve it already since I think there isnt much to change other than the review

[colinscz]

To me, this looks good, but I do not fully understand how it works.

Will it simply open up PRs for the new dependencies? Is it possible to tell it to avoid major upgrades?

Also might be worth rebasing since the package-lock.json has changed a bit @colinscz

I will approve it already since I think there isnt much to change other than the review

To answer your questions:

• Yes it will simply open up new PRs for any dependency updates.
• Yes you can customize it and exclude packages but I would have to double check how exactly you can configure or exclude major upgrades...worst case for now we can just abandon the PR made
• The lockfile topic had no influence in the PR so we should be good to go still