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

• .github/workflows/accurics.yaml (github-actions)
• .github/workflows/deploy.yml (github-actions)
• .github/workflows/publish.yml (github-actions)
• public/index.html (html)
• package.json (npm)

Configuration Summary

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

• Start dependency updates only once this onboarding PR is merged
• Enable Renovate Dependency Dashboard creation
• If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
• Ignore node_modules, bower_components, vendor and various test/tests directories
• Autodetect whether to pin dependencies or maintain ranges
• Rate limit PR creation to a maximum of two per hour
• Limit to maximum 10 open PRs at any time
• Group known monorepo packages together
• Use curated list of recommended non-monorepo package groupings
• Fix some problems with very old Maven commons versions
• Ignore spring cloud 1.x releases
• Ignore http4s digest-based 1.x milestones
• Use node versioning for @types/node
• Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

---

What to Expect

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

chore(deps): pin dependencies

• Schedule: ["at any time"]
• Branch name: renovate/pin-dependencies
• Merge into: master
• Pin @commitlint/cli to 13.1.0
• Pin @commitlint/config-conventional to 13.1.0
• Pin @dgiot/dgiot-mqtt-dashboard to 1.1.4
• Pin @vue/cli-plugin-babel to 4.5.13
• Pin @vue/cli-plugin-eslint to 4.5.13
• Pin @vue/cli-service to 4.5.13
• Pin babel-eslint to 10.1.0
• Pin babel-plugin-component to 1.1.1
• Pin commitizen to 4.2.4
• Pin conventional-changelog to 3.1.24
• Pin core-js to 3.17.3
• Pin cz-conventional-changelog to 3.3.0
• Pin cz-customizable to 6.3.0
• Pin element-ui to 2.15.6
• Pin eslint to 6.8.0
• Pin eslint-plugin-vue to 6.2.2
• Pin husky to 7.0.2
• Pin loadsh to 0.0.4
• Pin md5 to 2.3.0
• Pin moment to 2.29.1
• Pin sass to 1.42.1
• Pin sass-loader to 7.3.1
• Pin vue to 2.6.14
• Pin vue-template-compiler to 2.6.14
• Pin vuex to 3.6.2
• Pin vuex-persistedstate to 4.0.0

chore(deps): update dependency husky to v7.0.4

• Schedule: ["at any time"]
• Branch name: renovate/husky-7.x
• Merge into: master
• Upgrade husky to 7.0.4

chore(deps): update dependency paho-mqtt to v1.0.2

• Schedule: ["at any time"]
• Branch name: renovate/paho-mqtt-1.x
• Merge into: master
• Upgrade paho-mqtt to sha512-/DLt4+Ee4dtVAiyTMO7XsQ8ZCccddZRnVWPBeAtTdaT053JM2idaNP3o2thczXVqR6E8MjrLpqhY4x6om6nU7w==

chore(deps): update vue monorepo to v4.5.15

• Schedule: ["at any time"]
• Branch name: renovate/vue-monorepo
• Merge into: master
• Upgrade @vue/cli-plugin-babel to 4.5.15
• Upgrade @vue/cli-plugin-eslint to 4.5.15
• Upgrade @vue/cli-service to 4.5.15

fix(deps): update dependency @​dgiot/dgiot-mqtt-dashboard to v1.1.5

• Schedule: ["at any time"]
• Branch name: renovate/dgiot-dgiot-mqtt-dashboard-1.x
• Merge into: master
• Upgrade @dgiot/dgiot-mqtt-dashboard to 1.1.5

chore(deps): update commitlint monorepo

• Schedule: ["at any time"]
• Branch name: renovate/commitlint-monorepo
• Merge into: master
• Upgrade @commitlint/cli to 13.2.1
• Upgrade @commitlint/config-conventional to 13.2.0

fix(deps): update dependency core-js to v3.19.3

• Schedule: ["at any time"]
• Branch name: renovate/core-js-3.x
• Merge into: master
• Upgrade core-js to 3.19.3

fix(deps): update dependency sass to v1.45.0

• Schedule: ["at any time"]
• Branch name: renovate/sass-1.x
• Merge into: master
• Upgrade sass to 1.45.0

fix(deps): update dependency vuex-persistedstate to v4.1.0

• Schedule: ["at any time"]
• Branch name: renovate/vuex-persistedstate-4.x
• Merge into: master
• Upgrade vuex-persistedstate to 4.1.0

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

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-node-2.x
• Merge into: master
• Upgrade actions/setup-node to v2

chore(deps): update commitlint monorepo to v15 (major)

• Schedule: ["at any time"]
• Branch name: renovate/major-commitlint-monorepo
• Merge into: master
• Upgrade @commitlint/cli to 15.0.0
• Upgrade @commitlint/config-conventional to 15.0.0

chore(deps): update dependency eslint to v8

• Schedule: ["at any time"]
• Branch name: renovate/eslint-8.x
• Merge into: master
• Upgrade eslint to 8.4.1

chore(deps): update dependency eslint-plugin-vue to v8

• Schedule: ["at any time"]
• Branch name: renovate/eslint-plugin-vue-8.x
• Merge into: master
• Upgrade eslint-plugin-vue to 8.2.0

fix(deps): update dependency sass-loader to v12

• Schedule: ["at any time"]
• Branch name: renovate/sass-loader-12.x
• Merge into: master
• Upgrade sass-loader to 12.4.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam 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 WhiteSource Renovate. View repository job log here.

[vercel]

Deployment failed with the following error:

The most recent charge for your active payment method has failed. Please update it here: https://vercel.com/teams/dgiot-mqtt/settings/billing.

[pull-request-quantifier-deprecated]

This PR has 3 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +3 -0
Percentile : 1.2%

Total files changed: 1

Change summary by file extension:
.json : +3 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.