Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps-dev): bump stylelint from 13.13.1 to 15.10.1 #42

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jul 7, 2023

Bumps stylelint from 13.13.1 to 15.10.1.

Release notes

Sourced from stylelint's releases.

15.10.1

15.10.0

15.9.0

  • Added: insideFunctions: {"function": int} to number-max-precision (#6932) (@​romainmenke).
  • Fixed: declaration-block-no-redundant-longhand-properties autofix for border-radius shorthand (#6958) (@​mattxwang).
  • Fixed: declaration-block-no-redundant-longhand-properties autofix for border-width shorthand (#6956) (@​mattxwang).
  • Fixed: declaration-block-no-redundant-longhand-properties autofix for grid-column and grid-row (#6957) (@​mattxwang).

15.8.0

15.7.0

  • Added: splitList: boolean to selector-nested-pattern (#6896) (@​is2ei).
  • Fixed: unit-no-unknown false positives for unicode-range descriptors (#6892) (@​romainmenke).

... (truncated)

Changelog

Sourced from stylelint's changelog.

15.10.1

15.10.0

15.9.0

  • Added: insideFunctions: {"function": int} to number-max-precision (#6932) (@​romainmenke).
  • Fixed: declaration-block-no-redundant-longhand-properties autofix for border-radius shorthand (#6958) (@​mattxwang).
  • Fixed: declaration-block-no-redundant-longhand-properties autofix for border-width shorthand (#6956) (@​mattxwang).
  • Fixed: declaration-block-no-redundant-longhand-properties autofix for grid-column and grid-row (#6957) (@​mattxwang).

15.8.0

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by mattxwang, a new releaser for stylelint since your current version.


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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [stylelint](https://github.com/stylelint/stylelint) from 13.13.1 to 15.10.1.
- [Release notes](https://github.com/stylelint/stylelint/releases)
- [Changelog](https://github.com/stylelint/stylelint/blob/main/CHANGELOG.md)
- [Commits](stylelint/stylelint@13.13.1...15.10.1)

---
updated-dependencies:
- dependency-name: stylelint
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jul 7, 2023
@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: 1

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

@guardrails
Copy link

guardrails bot commented Jul 7, 2023

⚠️ We detected 27 security issues in this pull request:

Vulnerable Libraries (27)
Severity Details
High pkg:npm/[email protected] (t) upgrade to: 3.2.2,2.6.4
High pkg:npm/[email protected] (t) upgrade to: 6.0.1,5.0.1,4.1.1,3.0.1
High pkg:npm/[email protected] (t) upgrade to: 0.0.8
High pkg:npm/[email protected] (t) upgrade to: 6.0.1,5.0.1,4.1.1,3.0.1
Critical pkg:npm/[email protected] (t) upgrade to: 3.1.7
N/A pkg:npm/[email protected] (t) - no patch available
Critical pkg:npm/[email protected] (t) upgrade to: 1.1.1,2.0.2
High pkg:npm/[email protected] (t) upgrade to: 5.1.2
Critical pkg:npm/[email protected] (t) upgrade to: 0.4.0
Critical pkg:npm/[email protected] (t) upgrade to: 2.0.3
High pkg:npm/[email protected] (t) upgrade to: 2.2.2
Critical pkg:npm/[email protected] (t) upgrade to: 2.0.3
N/A pkg:npm/[email protected] (t) upgrade to: 2.2.2
High pkg:npm/[email protected] (t) upgrade to: 2.2.2
Critical pkg:npm/[email protected] (t) upgrade to: 2.0.3
Critical pkg:npm/[email protected] (t) upgrade to: 1.2.6
High pkg:npm/[email protected] (t) upgrade to: 2.0.1
High pkg:npm/[email protected] (t) upgrade to: 3.0.5
N/A pkg:npm/[email protected] (t) upgrade to: 1.0.0
Medium pkg:npm/[email protected] (t) upgrade to: 0.2.1,1.2.3
High pkg:npm/[email protected] (t) upgrade to: 4.17.3,6.10.3,6.9.7,6.8.3,6.7.3,6.6.1,6.5.3,6.4.1,6.3.3,6.2.4
High pkg:npm/[email protected] (t) upgrade to: 4.17.3,6.10.3,6.9.7,6.8.3,6.7.3,6.6.1,6.5.3,6.4.1,6.3.3,6.2.4
N/A pkg:npm/[email protected] (t) - no patch available
Critical pkg:npm/[email protected] (t) upgrade to: 1.7.3
Medium pkg:npm/[email protected] (t) upgrade to: 4.8.1,5.14.2
Medium pkg:npm/[email protected] (t) upgrade to: 1.5.7
N/A pkg:npm/[email protected] (t) upgrade to: 2.2.2

More info on how to fix Vulnerable Libraries in JavaScript.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

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.

0 participants