ivangabriele / vscode-heroku

Check your project's Heroku deployment status in Visual Studio Code.
https://marketplace.visualstudio.com/items?itemName=ivangabriele.vscode-heroku
MIT License
9 stars 8 forks source link

build(dev-deps): update dependency lint-staged to v15 #265

Open renovate[bot] opened 12 months ago

renovate[bot] commented 12 months ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lint-staged 13.2.3 -> 15.2.5 age adoption passing confidence

Release Notes

okonet/lint-staged (lint-staged) ### [`v15.2.5`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#1525) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v15.2.4...v15.2.5) ##### Patch Changes - [#​1424](https://togithub.com/lint-staged/lint-staged/pull/1424) [`31a1f95`](https://togithub.com/lint-staged/lint-staged/commit/31a1f9548ea8202bc5bd718076711f747396e3ca) Thanks [@​iiroj](https://togithub.com/iiroj)! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available. - [#​1423](https://togithub.com/lint-staged/lint-staged/pull/1423) [`91abea0`](https://togithub.com/lint-staged/lint-staged/commit/91abea0d298154d92113ba34bae4020704e22918) Thanks [@​iiroj](https://togithub.com/iiroj)! - Improve error logging when failing to read or parse a configuration file - [#​1424](https://togithub.com/lint-staged/lint-staged/pull/1424) [`ee43f15`](https://togithub.com/lint-staged/lint-staged/commit/ee43f154097753dd5448766f792387e60e0ea453) Thanks [@​iiroj](https://togithub.com/iiroj)! - Upgrade micromatch@4.0.7 ### [`v15.2.4`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#1524) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v15.2.2...v15.2.4) ##### Patch Changes - [`4f4537a`](https://togithub.com/lint-staged/lint-staged/commit/4f4537a75ebfba816826f6f67a325dbc7f25908a) Thanks [@​iiroj](https://togithub.com/iiroj)! - Fix release issue with previous version; update dependencies ### [`v15.2.2`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#1522) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v15.2.1...v15.2.2) ##### Patch Changes - [#​1391](https://togithub.com/lint-staged/lint-staged/pull/1391) [`fdcdad4`](https://togithub.com/lint-staged/lint-staged/commit/fdcdad42ff96fea3c05598e378d3c44ad4a51bde) Thanks [@​iiroj](https://togithub.com/iiroj)! - *Lint-staged* no longer tries to load configuration from files that are not checked out. This might happen when using sparse-checkout. ### [`v15.2.1`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#1521) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v15.2.0...v15.2.1) ##### Patch Changes - [#​1387](https://togithub.com/lint-staged/lint-staged/pull/1387) [`e4023f6`](https://togithub.com/lint-staged/lint-staged/commit/e4023f687616dcf4816545b8eefbcce50e255c9c) Thanks [@​iiroj](https://togithub.com/iiroj)! - Ignore stdin of spawned commands so that they don't get stuck waiting. Until now, *lint-staged* has used the default settings to spawn linter commands. This means the `stdin` of the spawned commands has accepted input, and essentially gotten stuck waiting. Now the `stdin` is ignored and commands will no longer get stuck. If you relied on this behavior, please open a new issue and describe how; the behavior has not been intended. ### [`v15.2.0`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#1520) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v15.1.0...v15.2.0) ##### Minor Changes - [#​1371](https://togithub.com/lint-staged/lint-staged/pull/1371) [`f3378be`](https://togithub.com/lint-staged/lint-staged/commit/f3378be894fb84800341800b1e4f6f8bc8dfd904) Thanks [@​iiroj](https://togithub.com/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](https://togithub.com/lint-staged/lint-staged/pull/1362) [`17bc480`](https://togithub.com/lint-staged/lint-staged/commit/17bc480c0f8767407a87527931558de8d1d1551d) Thanks [@​antonk52](https://togithub.com/antonk52)! - update lilconfig@3.0.0 - [#​1368](https://togithub.com/lint-staged/lint-staged/pull/1368) [`7c55ca9`](https://togithub.com/lint-staged/lint-staged/commit/7c55ca9f410043016e8b33b3b523b9b7e764acf4) Thanks [@​iiroj](https://togithub.com/iiroj)! - Update most dependencies - [#​1368](https://togithub.com/lint-staged/lint-staged/pull/1368) [`777d4e9`](https://togithub.com/lint-staged/lint-staged/commit/777d4e976852af4c181ffbe055f3531343349695) Thanks [@​iiroj](https://togithub.com/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](https://togithub.com/lint-staged/lint-staged/pull/1373) [`85eb0dd`](https://togithub.com/lint-staged/lint-staged/commit/85eb0ddab1eba0c0bcc8cc109e17dc2bbb3d044e) Thanks [@​iiroj](https://togithub.com/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`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#1510) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v15.0.2...v15.1.0) ##### Minor Changes - [#​1344](https://togithub.com/lint-staged/lint-staged/pull/1344) [`0423311`](https://togithub.com/lint-staged/lint-staged/commit/04233115a5e25d6fa7d357cbe9d42173ae8a1acf) Thanks [@​danielbayley](https://togithub.com/danielbayley)! - Add support for loading configuration from `package.yaml` and `package.yml` files, supported by `pnpm`. ##### Patch Changes - [#​1355](https://togithub.com/lint-staged/lint-staged/pull/1355) [`105d901`](https://togithub.com/lint-staged/lint-staged/commit/105d9012fc92fca549987816406450075cf255f3) Thanks [@​iiroj](https://togithub.com/iiroj)! - Suppress some warnings when using the "--quiet" flag ### [`v15.0.2`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#1502) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v15.0.1...v15.0.2) ##### Patch Changes - [#​1339](https://togithub.com/lint-staged/lint-staged/pull/1339) [`8e82364`](https://togithub.com/lint-staged/lint-staged/commit/8e82364dd89155e96de574cfb38a94d28b8635af) Thanks [@​iiroj](https://togithub.com/iiroj)! - Update dependencies, including listr2@​7.0.2 to fix an upstream issue affecting lint-staged. ### [`v15.0.1`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#1501) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v15.0.0...v15.0.1) ##### Patch Changes - [#​1217](https://togithub.com/lint-staged/lint-staged/pull/1217) [`d2e6f8b`](https://togithub.com/lint-staged/lint-staged/commit/d2e6f8b1e1cd84ba6eb2f3f6a7f650c882987041) Thanks [@​louneskmt](https://togithub.com/louneskmt)! - Previously it was possible for a function task to mutate the list of staged files passed to the function, and accidentally affect the generation of other tasks. This is now fixed by passing a copy of the original file list instead. ### [`v15.0.0`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#1500) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v14.0.1...v15.0.0) ##### Major Changes - [#​1322](https://togithub.com/okonet/lint-staged/pull/1322) [`66b93aa`](https://togithub.com/okonet/lint-staged/commit/66b93aac870d155ca81302b2574617da99409ca7) Thanks [@​iiroj](https://togithub.com/iiroj)! - **Require at least Node.js 18.12.0** This release drops support for Node.js 16, which is EOL after 2023-09-11. Please upgrade your Node.js to the latest version. Additionally, all dependencies have been updated to their latest versions. ### [`v14.0.1`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#v1401---21-Aug-2023) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v14.0.0...v14.0.1) ##### Bug Fixes - fix reading config from stdin, introduced in v14.0.0 ([#​1317](https://togithub.com/okonet/lint-staged/issues/1317)) ([fc3bfea](https://togithub.com/okonet/lint-staged/commit/fc3bfeabae29b65f99b6911a989b0b41d3d1128e)) ### [`v14.0.0`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#v1400---13-Aug-2023) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v13.3.0...v14.0.0) ##### Features - drop support for Node.js 14 ([#​1312](https://togithub.com/okonet/lint-staged/issues/1312)) ([9da8777](https://togithub.com/okonet/lint-staged/commit/9da877711a7547b9122c6af91683fb2a2f398184)) ##### BREAKING CHANGES - Please upgrade your Node.js version to at least `16.14.0`. ### [`v13.3.0`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#v1330---13-Aug-2023) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v13.2.3...v13.3.0) ##### Bug Fixes - **dependencies:** update most dependencies ([7443870](https://togithub.com/okonet/lint-staged/commit/7443870b2c24ead8613295cbfa1fe80f96167e1c)) - detect duplicate redundant braces in pattern ([d895aa8](https://togithub.com/okonet/lint-staged/commit/d895aa8382b769f841c6bdc52ba59755bb0ed28b)) ##### Features - **dependencies:** update `listr2@​6.6.0` ([09844ca](https://togithub.com/okonet/lint-staged/commit/09844ca3f6b99feba8f3c0ea10e60a6e6df511ad))

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone Europe/Paris, Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.



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

coderabbitai[bot] commented 4 months ago

[!IMPORTANT]

Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.