chore(deps): pin dependencies

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
@vue/cli-plugin-babel	devDependencies	pin	^4.5.14 -> 4.5.15
@vue/cli-plugin-eslint	devDependencies	pin	^4.5.14 -> 4.5.15
@vue/cli-plugin-router	devDependencies	pin	^4.5.14 -> 4.5.15
@vue/cli-plugin-vuex	devDependencies	pin	^4.5.14 -> 4.5.15
@vue/cli-service (source)	devDependencies	pin	^4.5.14 -> 4.5.15
@vue/eslint-config-airbnb	devDependencies	pin	^5.0.2 -> 5.3.0
@vue/eslint-config-prettier	devDependencies	pin	^6.0.0 -> 6.0.0
babel-eslint	devDependencies	pin	^10.1.0 -> 10.1.0
babel-plugin-transform-remove-console	devDependencies	pin	^6.9.4 -> 6.9.4
compression-webpack-plugin	devDependencies	pin	^6.1.1 -> 6.1.1
eslint (source)	devDependencies	pin	^6.8.0 -> 6.8.0
eslint-plugin-vue (source)	devDependencies	pin	^6.2.2 -> 6.2.2
sass	devDependencies	pin	^1.26.5 -> 1.45.0
sass-loader	devDependencies	pin	^8.0.2 -> 8.0.2
webpack	devDependencies	pin	^4.44.2 -> 4.46.0

📌 Important: Renovate will wait until you have merged this Pin PR before creating any upgrade PRs for the affected packages. Add the preset :preserveSemverRanges to your config if you instead don't wish to pin dependencies.

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Medium
Size       : +83 -74
Percentile : 51.4%

Total files changed: 2

Change summary by file extension:
.json : +15 -15
.yaml : +68 -59

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.