fix(deps): update dependencies (non-major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@babel/core (source)	^7.20.7 -> ^7.20.12
@typescript-eslint/eslint-plugin	^5.47.1 -> ^5.48.0
@typescript-eslint/parser	^5.47.1 -> ^5.48.0
babel-loader	^9.1.0 -> ^9.1.2
ci-info	^3.7.0 -> ^3.7.1
eslint-config-prettier	^8.5.0 -> ^8.6.0
eslint-plugin-jsonc (source)	^2.5.0 -> ^2.6.0
lerna (source)	^6.3.0 -> ^6.4.0

---

Release Notes

babel/babel

v7.20.12

Compare Source

🐛 Bug Fix

• babel-traverse
  • #​15224 Fix TaggedTemplateLiteral evaluation (@​nmn)
• babel-helper-create-class-features-plugin, babel-plugin-proposal-class-properties
  • #​15312 fix: delete this in static class properties initialization (@​SuperSodaSea)

💅 Polish

• babel-traverse
  • #​15313 Implement support for evaluating computed properties. (@​JBYoshi)

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.48.0

Compare Source

Features

• eslint-plugin: specify which method is unbound and added test case (#​6281) (cf3ffdd)

5.47.1 (2022-12-26)

Bug Fixes

• ast-spec: correct some incorrect ast types (#​6257) (0f3f645)
• eslint-plugin: [member-ordering] correctly invert optionalityOrder (#​6256) (ccd45d4)

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.48.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

5.47.1 (2022-12-26)

Note: Version bump only for package @​typescript-eslint/parser

babel/babel-loader

v9.1.2

Compare Source

9.1.1 was a broken release, it didn't include all the commits.

Dependencies updates

• Bump qs from 6.5.2 to 6.5.3 by @​dependabot in https://github.com/babel/babel-loader/pull/977
• Bump json5 from 2.2.1 to 2.2.3 by @​dependabot in https://github.com/babel/babel-loader/pull/980

Misc

• GitHub Workflows security hardening by @​sashashura in https://github.com/babel/babel-loader/pull/976

New Contributors

• @​sashashura made their first contribution in https://github.com/babel/babel-loader/pull/976

Full Changelog: babel/babel-loader@v9.1.0...v9.1.2

v9.1.1

Compare Source

watson/ci-info

v3.7.1

Compare Source

• ignore ci detection when CI is set to 'false' 24cc450

prettier/eslint-config-prettier

v8.6.0

Compare Source

• Added: [vue/multiline-ternary]. Thanks to @​xcatliu!

ota-meshi/eslint-plugin-jsonc

v2.6.0

Compare Source

Minor Changes

• #​205 05be0a9 Thanks @​danielrentz! - disable no-unused-vars in base config

lerna/lerna

v6.4.0

Compare Source

Features

• watch: Add lerna watch command (#​3466) (008b995)

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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, check this box

---

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

[pull-request-quantifier-deprecated]

This PR has 26 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       : +13 -13
Percentile : 10.4%

Total files changed: 8

Change summary by file extension:
.json : +13 -13
.lock : +0 -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 detected.
• 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.

[codecov]

Codecov Report

Merging #875 (ca77a59) into main (7a72ace) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #875   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines           57        57           
  Branches         2         2           
=========================================
  Hits            57        57           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.