Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Dec 11, 2023

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/ci.yml (github-actions)
  • .github/workflows/release.yml (github-actions)
  • .node-version (nodenv)
  • package.json (npm)
  • playground/package.json (npm)
  • pnpm-workspace.yaml (npm)
  • renovate.json (renovate-config-presets)

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
  • Group all minor and patch updates together.
  • Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
  • Schedule automerge for the first day of each month, before 4 AM.
  • Automerge non-major upgrades for semver stable packages if they pass tests.
  • Preserve (but continue to upgrade) any existing SemVer ranges.

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

chore(deps): replace dependency @​tsconfig/node18 with @tsconfig/node20
  • Schedule: ["at any time"]
  • Branch name: renovate/tsconfig-node18-replacement
  • Merge into: main
  • Upgrade @tsconfig/node18 to ^20.1.0
fix(deps): update @dcloudio
fix(deps): update all non-major dependencies
  • Schedule: ["at any time"]
  • Branch name: renovate/all-minor-patch
  • Merge into: main
  • Upgrade markdownlint-cli to ^0.47.0
  • Upgrade pnpm to 8.15.9
  • Upgrade publint to ^0.3.0
  • Upgrade taze to ^0.18.0
  • Upgrade typescript to 5.9.3
  • Upgrade vite to 4.5.14
  • Upgrade vue to 3.5.25
  • Upgrade vue-i18n to 9.14.5
chore(deps): update commitlint monorepo to v20 (major)
chore(deps): update dependency @​modyqyw/fabric to v11
  • Schedule: ["at any time"]
  • Branch name: renovate/modyqyw-fabric-11.x
  • Merge into: main
  • Upgrade @modyqyw/fabric to ^11.0.0
chore(deps): update dependency bumpp to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/bumpp-10.x
  • Merge into: main
  • Upgrade bumpp to ^10.0.0
chore(deps): update dependency concurrently to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/concurrently-9.x
  • Merge into: main
  • Upgrade concurrently to ^9.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 is-ci to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/is-ci-4.x
  • Merge into: main
  • Upgrade is-ci to ^4.0.0
chore(deps): update dependency lint-staged to v16
  • Schedule: ["at any time"]
  • Branch name: renovate/lint-staged-16.x
  • Merge into: main
  • Upgrade lint-staged to ^16.0.0
chore(deps): update dependency taze to v19
  • Schedule: ["at any time"]
  • Branch name: renovate/taze-19.x
  • Merge into: main
  • Upgrade taze to ^19.0.0
chore(deps): update dependency tsx to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/tsx-4.x
  • Merge into: main
  • Upgrade tsx to ^4.0.0
chore(deps): update dependency unbuild to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/unbuild-3.x
  • Merge into: main
  • Upgrade unbuild to ^3.0.0
chore(deps): update dependency vite to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/vite-7.x
  • Merge into: main
  • Upgrade vite to 7.3.0
chore(deps): update pnpm to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-10.x
  • Merge into: main
  • Upgrade pnpm to 10.26.0
chore(deps): update typescript-eslint monorepo to v8 (major)
fix(deps): update dependency vue-i18n to v11
  • Schedule: ["at any time"]
  • Branch name: renovate/vue-i18n-11.x
  • Merge into: main
  • Upgrade vue-i18n to 11.2.2

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant