Skip to content

Conversation

@dependabot-preview
Copy link
Contributor

Bumps @vue/cli-plugin-eslint from 4.3.1 to 4.5.13.

Release notes

Sourced from @​vue/cli-plugin-eslint's releases.

v4.5.13

🐛 Bug Fix

  • @vue/babel-preset-app
    • #6459 fix: fix modern mode optional chaining syntax tranpilation (@​sodatea)
  • @vue/cli-plugin-unit-mocha
  • @vue/cli-service

Others

Committers: 3

v4.5.12

  • bump vue-codemod to work around an NPM hoisting bug
  • bump minimum required JSX preset / plugin versions, fixes vuejs/jsx#183
  • bump default typescript version to 4.1 and prettier version to 2.x for new projects, fixes #6299

v4.5.11

🐛 Bug Fix

Committers: 1

v4.5.10

🐛 Bug Fix

  • @vue/cli-plugin-unit-mocha
  • @vue/cli-plugin-unit-mocha, @vue/cli-service
  • @vue/cli-ui
  • @vue/cli-service-global, @vue/cli-service

Committers: 3

... (truncated)

Changelog

Sourced from @​vue/cli-plugin-eslint's changelog.

4.5.13 (2021-05-08)

🐛 Bug Fix

  • @vue/babel-preset-app
    • #6459 fix: fix modern mode optional chaining syntax tranpilation (@​sodatea)
  • @vue/cli-plugin-unit-mocha
  • @vue/cli-service

Others

Committers: 3

4.5.12 (2021-03-17)

  • bump vue-codemod to work around an NPM hoisting bug
  • bump minimum required JSX preset / plugin versions, fixes vuejs/jsx#183
  • bump default typescript version to 4.1 and prettier version to 2.x for new projects, fixes #6299

4.5.11 (2021-01-22)

🐛 Bug Fix

Committers: 1

4.5.10 (2021-01-06)

🐛 Bug Fix

  • @vue/cli-plugin-unit-mocha
  • @vue/cli-plugin-unit-mocha, @vue/cli-service
  • @vue/cli-ui
  • @vue/cli-service-global, @vue/cli-service

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@pull-request-quantifier-deprecated

This PR has 2 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       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1

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.

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

Labels

dependencies Pull requests that update a dependency file Extra Small

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant