search

dev-AshishRanjan / Idea-Arca

Idea Arca (Latin: "Idea Vault") is a Project Idea Bank. Unleash your tech creativity. Discover, collaborate, and bring to life innovative project ideas in various tech fields through this inspirational repository.
https://idea-arca.vercel.app
MIT License
6 stars 8 forks source link

chore(deps)[npm]: bump lint-staged from 15.0.2 to 15.2.0 #55

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 7 months ago

Bumps lint-staged from 15.0.2 to 15.2.0.

Release notes

Sourced from lint-staged's releases.

v15.2.0

Minor Changes

  • #1371 f3378be Thanks @​iiroj! - Using the --no-stash flag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag --no-hide-partially-staged that is automatically enabled when --no-stash is used.

Patch Changes

  • #1362 17bc480 Thanks @​antonk52! - update lilconfig@3.0.0

  • #1368 7c55ca9 Thanks @​iiroj! - Update most dependencies

  • #1368 777d4e9 Thanks @​iiroj! - To improve performance, only use lilconfig when searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.

  • #1373 85eb0dd Thanks @​iiroj! - When determining git directory, use fs.realpath() only for symlinks. It looks like fs.realpath() changes some Windows mapped network filepaths unexpectedly, causing issues.

v15.1.0

Minor Changes

  • #1344 0423311 Thanks @​danielbayley! - Add support for loading configuration from package.yaml and package.yml files, supported by pnpm.

Patch Changes

Changelog

Sourced from lint-staged's changelog.

15.2.0

Minor Changes

  • #1371 f3378be Thanks @​iiroj! - Using the --no-stash flag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag --no-hide-partially-staged that is automatically enabled when --no-stash is used.

Patch Changes

  • #1362 17bc480 Thanks @​antonk52! - update lilconfig@3.0.0

  • #1368 7c55ca9 Thanks @​iiroj! - Update most dependencies

  • #1368 777d4e9 Thanks @​iiroj! - To improve performance, only use lilconfig when searching for config files outside the git repo. In the regular case, lint-staged finds the config files from the Git index and loads them directly.

  • #1373 85eb0dd Thanks @​iiroj! - When determining git directory, use fs.realpath() only for symlinks. It looks like fs.realpath() changes some Windows mapped network filepaths unexpectedly, causing issues.

15.1.0

Minor Changes

  • #1344 0423311 Thanks @​danielbayley! - Add support for loading configuration from package.yaml and package.yml files, supported by pnpm.

Patch Changes

Commits
  • adf50b0 chore(changeset): release
  • 85eb0dd fix: when determining git directory, use fs.realpath() only for symlinks
  • 82eded4 refactor: use commander implies() syntax for flag
  • f3378be feat: --no-stash flag implies --no-hide-partially-staged
  • f4f61f3 docs: add workaround for verbose Windows output to README FAQ
  • 17bc480 chore(deps): update lilconfig@3.0.0
  • eccda41 style: remove Babel from ESLint
  • 077e6bc test: run Jest tests in native ESM mode
  • 8db4a15 refactor: move config file name constants to separate file
  • 78a0c23 test: add missing test coverage
  • Additional commits viewable in compare view


Dependabot compatibility score

You can trigger a rebase of this PR 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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

vercel[bot] commented 7 months ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
idea-arca ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 4, 2023 7:53pm
pr-explainer-bot[bot] commented 7 months ago

Pull Request Report

Hey there! Here's a report on the changes made in the pull request:

Changes

  1. Bumped lint-staged from version 15.0.2 to 15.2.0.

Suggestions

No suggestions provided.

Bugs

No bugs found.

Improvements

No improvements suggested.

Rating

Please rate the code on a scale of 0 to 10 based on the following criteria:

Feel free to provide a brief explanation for your rating.

That's it for the report! Let me know if you need any further assistance.

sweep-ai[bot] commented 7 months ago

Apply Sweep Rules to your PR?

vizipi[bot] commented 7 months ago

Pull request analysis by VIZIPI

Below you will find who is the most qualified team member to review your code. This analysis includes his/her work on the code included in this Pull request, in addition to their experience in code affected by these changes ( partly found within the list of potential missing files below )   Feedback always welcome

No other active qualified developers found to review these specific changes. You might consider involving more team members with these code segments.

Potential missing files from this Pull request

No commonly committed files found with a 40% threashold

Committed file ranks

  • 95.45%[package.json]
  • 97.73%[package-lock.json]
    • pull-request-quantifier-deprecated[bot] commented 7 months ago

    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](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

    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](https://github.com/microsoft/PullRequestQuantifier/releases) - 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](./docs/prquantifier-yaml.md) 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? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

    dependabot[bot] commented 2 months ago

    Superseded by #78.