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): update code formatter packages (major) #148

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 8, 2021

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
husky 4.3.0 -> 9.1.6 age adoption passing confidence
lint-staged 10.5.2 -> 15.2.10 age adoption passing confidence
prettier (source) 2.2.0 -> 3.3.3 age adoption passing confidence
sort-package-json 1.48.0 -> 2.10.1 age adoption passing confidence

Release Notes

typicode/husky (husky)

v9.1.6

Compare Source

v9.1.5

Compare Source

v9.1.4

Compare Source

v9.1.3

Compare Source

  • fix: better handle space in PATH

v9.1.2

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

Super saiyan god dog! It's over 9.0.0!

There's a bug with this release which prevents the deprecation notice to appear and requires to remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" (which are deprecated by the way). I'll publish a new version to fix that. Sorry about any inconvenience.

What's new

You can now run package commands directly, no need for npx or equivalents.
It makes writing hooks more intuitive and is also slightly faster 🐺⚡️

### .husky/pre-commit
- npx jest
+ jest # ~0.2s faster

A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.

### .husky/pre-commit
prettier $(git diff --cached --name-only --diff-filter=ACMR | sed 's| |\\ |g') --write --ignore-unknown
git update-index --again

For more advanced use cases, see lint-staged.

Fixes

  • bunx husky init command
  • Workaround for some hooks implementation on Windows 🤷

Deprecations

  • Remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" from your hooks
  • Move your code from ~/.huskyrc to .config/husky/init.sh

Support for these will be removed in v10, notices have been added.

Friendly reminder

If Git hooks don't fit your workflow, you can disable Husky globally. Just add export HUSKY=0 to .config/husky/init.sh.

I've seen some confusion about this on X, so just a heads-up!

Sponsoring

Husky is downloaded over 45M times per month and used by ~1.5M projects. If your company wants to sponsor, you can do so here: GitHub Sponsors.

Have a nice summer ☀️ I'm open to new opportunities/consulting so feel free to drop me a message 😉

v9.0.11

Compare Source

v9.0.10

Compare Source

v9.0.9

Compare Source

v9.0.8

Compare Source

v9.0.7

Compare Source

v9.0.6

Compare Source

v9.0.5

Compare Source

v9.0.4

Compare Source

v9.0.3

Compare Source

v9.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.0.1...v9.0.2

v9.0.1

Compare Source

Kicking off the year with an exciting update!

TLDR;

Improved user experience and a (even) smaller package size while packing in more features!

👋 By the Way

I'm available for remote work (Front-end/Back-end mainly JS/TS but open to other stacks Rails, Go, Elixir). You can contact me at my mail: typicode at gmail 🙂

Introducing husky init

Adding husky to a project is now easier than ever. Although the installation process was straightforward, it often required consulting the documentation.

v8
npm pkg set scripts.prepare="husky install"
npm run prepare
npx husky add .husky/pre-commit "npm test"
v9
npx husky init

Adding a New Hook

Adding a hook is now as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic echo command.

v8
npx husky add  .husky/pre-commit "npm test"
git add --chmod=+x .husky/pre-commit # On Windows
v9
echo "npm test" > .husky/pre-commit

Further Size Reduction

v8 was already the most compact Git hooks manager at approximately 6kB.

v9 takes this a step further, reducing the size to just 3kB, likely making it the smallest devDependency in your toolkit.

To give you an idea of how small it is, the biggest file in the project is the MIT license 😄

More to Come

Additional features are in the pipeline for v9. Stay tuned 🙌

Other Changes

  • Enhanced security with CI and npm --provenance for safer publishing.
  • Added $XDG_CONFIG_HOME support. Move ~/.huskyrc to ~/.config/husky/init.sh for centralized configuration.
  • Fixed permission issue for Windows-created hooks; they no longer need to be executable.
  • Removed husky install. Use husky or husky some/dir for the same functionality (deprecation notice to be added).
  • Modified behavior when .git is missing; it now triggers a warning instead of failure.
  • Replaced HUSKY_DEBUG=1 with HUSKY=2 for debugging.
  • Updated the Husky API for module usage.
  • Transitioned to ESM for module usage.
  • Dropped support for Node 14 and 16.
  • Revamped docs.

How to Migrate

v9 is backward compatible with v8, allowing you to freely upgrade and migrate your hooks later.

package.json

{
  "scripts": {
-   "prepare": "husky install"
+   "prepare": "husky"
  }
}

.husky/pre-commit

- #!/usr/bin/env sh
- . "$(dirname -- "$0")/_/husky.sh"
npm test

v8.0.3

Compare Source

  • fix: add git not installed message #​1208

v8.0.2

Compare Source

  • docs: remove deprecated npm set-script

v8.0.1

Compare Source

  • fix: use POSIX equality operator

v8.0.0

Compare Source

What's Changed

Feats
Fixes
Docs
Chore

v7.0.4

Compare Source

No changes. Husky v7.0.3 was reverted, this version is the same as v7.0.2.

v7.0.3

Compare Source

v7.0.2

Compare Source

Fix pre-commit hook in WebStorm (#​1023)

v7.0.1

Compare Source

  • Fix gracefully fail if Git command is not found #​1003 (same as in v6)

v7.0.0

Compare Source

  • Improve .husky/ directory structure. .husky/.gitignore is now unnecessary and can be removed.
  • Improve error output (shorter)
  • Update husky-init CLI
  • Update husky-4-to-7 CLI
  • Drop Node 10 support

Please help me develop and release OSS projects ❤️ on GitHub Sponsors or Open Collective. Thank you for your support!

v6.0.0

Compare Source

After being in early access for Open Source projects and Sponsors for a limited time, I'm happy to announce that husky 6 is MIT again and can be freely used in commercial projects! 🎉

Many thanks to the Open Source projects and Companies which have switched to/sponsored the new husky during this period!

OSS is my full-time job, please consider sponsoring the development of husky on GitHub sponsors or Open Collective. Thank you!

Breaking change

  • husky init has been moved to its own package (npx husky-init)

Added

  • Programmatically use husky: require('husky')
  • TypeScript definitions

Migrating from husky 4

Husky 6 contains breaking changes. If you're coming from v4, npm install husky@6 won't be enough.

Recommended: see husky-4-to-6 CLI to automatically migrate your config. There's also a dedicated section in the docs.

If you're curious why config has changed, you may be interested in reading:
https://blog.typicode.com/husky-git-hooks-javascript-config/

Also Husky 6 follows official npm and Yarn best practices regarding autoinstall. It's recommended to use prepare script instead (see usage in docs).

v5.2.0

Compare Source

  • Add set command to replace hooks (husky set .husky/pre-commit cmd)
  • Update add command to append command (husky add .husky/pre-commit cmd)
  • Improve error messages

v5.1.3

Compare Source

  • docs: add specific Yarn v2 install/uninstall instructions
  • cli: husky init will detect Yarn v2 and initialize accordingly

v5.1.2

Compare Source

  • docs: recommend prepare script instead of postinstall (#​890)
  • cli: husky init use prepare script (#​890)

v5.1.1

Compare Source

  • style(shell): add trailing newlines (#​870)
  • fix(init): update package.json postinstall

v5.1.0

Compare Source

  • Add husky init

v5.0.9

Compare Source

  • fix(install): do not fail if not inside a Git directory (closes #​851)

See https://github.com/typicode/husky/releases/tag/v5.0.0 for v5 release notes

v5.0.8

Compare Source

v5.0.7

Compare Source

  • fix(shell): double quote params (#​824)

v5.0.6

Compare Source

  • Remove unused files

v5.0.5

Compare Source

  • Fix custom directory support #​827

v5.0.4

Compare Source

v5.0.3

Compare Source

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

👉 See https://typicode.github.io/husky for breaking changes and new installation instructions.

Note about the license

Husky 5 is released under The Parity Public License.

It doesn't affect you if you're using husky in an Open Source project or if you're a sponsor. You're free to use it as usual and I hope you'll enjoy this new release ❤️

If you're using husky in a commercial project, you may want to consider becoming a sponsor to support the project. You can also try it for 30 days.

This is only for a limited time, husky will be MIT again later.

Migrating

Important Husky v5 brings a lot of improvements but is also very different from v4. Git hooks won't work if you only upgrade husky dependency, existing config needs to be migrated too.

The best way to switch to v5 is to follow the new installation instructions and migrate existing hooks command using husky add.

v4.3.8

Compare Source

  • Fix Cannot read property 'toString' of null
  • Improve error messages

v4.3.7

Compare Source

v4.3.6

Compare Source

  • Fix prepare-commit-msg on windows #​737

v4.3.5

Compare Source

  • Rollback and do not throw error if husky install fails

v4.3.4

Compare Source

  • Throw error if husky install fails
  • Add workaround for npm 7 currently missing INIT_CWD environment variable

v4.3.3

Compare Source

v4.3.2

Compare Source

v4.3.1

Compare Source

lint-staged/lint-staged (lint-staged)

v15.2.10

Compare Source

Patch Changes

v15.2.9

Compare Source

Patch Changes
  • #​1463 b69ce2d Thanks @​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning MaxListenersExceededWarning: Possible EventEmitter memory leak detected.

v15.2.8

Compare Source

Patch Changes
  • f0480f0 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version switched the --show-toplevel flag with --show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js child_process. The new flag returns a path relative to the working directory, avoiding the issue.

    The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.

v15.2.7

Compare Source

Patch Changes
  • #​1440 a51be80 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.

v15.2.6

Compare Source

Patch Changes
  • #​1433 119adb2 Thanks @​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.

v15.2.5

Compare Source

Patch Changes
  • #​1424 31a1f95 Thanks @​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 91abea0 Thanks @​iiroj! - Improve error logging when failing to read or parse a configuration file

  • #​1424 ee43f15 Thanks @​iiroj! - Upgrade micromatch@4.0.7

v15.2.4

Compare Source

Patch Changes
  • 4f4537a Thanks @​iiroj! - Fix release issue with previous version; update dependencies

v15.2.2

Compare Source

Patch Changes
  • #​1391 fdcdad4 Thanks @​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

Compare Source

Patch Changes
  • #​1387 e4023f6 Thanks @​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

Compare Source

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

Compare Source

Minor Changes
Patch Changes

v15.0.2

Compare Source

Patch Changes
  • #​1339 8e82364 Thanks @​iiroj! - Update dependencies, including listr2@​7.0.2 to fix an upstream issue affecting lint-staged.

v15.0.1

Compare Source

Patch Changes
  • #​1217 d2e6f8b Thanks @​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

Compare Source

Major Changes
  • #​1322 66b93aa Thanks @​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

Compare Source

Bug Fixes
  • fix reading config from stdin, introduced in v14.0.0 (#​1317) (fc3bfea)

v14.0.0

Compare Source

Features
BREAKING CHANGES
  • Please upgrade your Node.js version to at least 16.14.0.

v13.3.0

Compare Source

Bug Fixes
  • dependencies: update most dependencies (7443870)
  • detect duplicate redundant braces in pattern (d895aa8)
Features
  • dependencies: update listr2@​6.6.0 (09844ca)

v13.2.3

Compare Source

Bug Fixes
  • the --diff option implies --no-stash (66a716d)

v13.2.2

Compare Source

Bug Fixes

v13.2.1

Compare Source

Bug Fixes
  • ignore "package.json" as config file when it's invalid JSON (#​1281) (e7ed6f7)

v13.2.0

Compare Source

Bug Fixes
  • dependencies: replace colorette with chalk for better color support detection (f598725)
  • use index-based stash references for improved MSYS2 compatibility (#​1270) (60fcd99)
Features

v13.1.4

Compare Source

v13.1.3

Compare Source

v13.1.2

Compare Source

Bug Fixes

v13.1.1

Compare Source

Bug Fixes
  • allow re-enabling --stash when using the --diff option (99390c3)

v13.1.0

Compare Source

Features

v13.0.4

Compare Source

Bug Fixes
  • deps: update all dependencies (336f3b5)
  • deps: update all dependencies (ec995e5)

v13.0.3

Compare Source

Bug Fixes

v13.0.2

Compare Source

Bug Fixes
  • use new --diff and --diff-filter options when checking task modifications (1a5a66a)

v13.0.1

Compare Source

Bug Fixes
  • correct spelling of "0 files" (f27f1d4)
  • suppress error from process.kill when killing tasks on failure (f2c6bdd)
  • deps: update pidtree@^0.6.0 to fix screen size error in WSL (1a77e42)
  • ignore "No matching pid found" error (cb8a432)
  • prevent possible race condition when killing tasks on failure (bc92aff)
Performance Improvements
  • use EventsEmitter instead of setInterval for killing tasks on failure (c508b46)

v13.0.0

Compare Source

Bug Fixes
  • deps: update execa@^6.1.0 (659c85c)
  • deps: update yaml@^2.1.1 (2750a3d)
Features
  • remove support for Node.js 12 (5fb6df9)
BREAKING CHANGES
  • lint-staged will no longer support Node.js 12, which is EOL since 30 April 2022

v12.5.0

Compare Source

Bug Fixes
  • include all files when using --config <path> (641d1c2)
  • skip backup stash when using the --diff option (d4da24d)
Features
  • add --diff-filter option for overriding list of (staged) files (753ef72)
  • add --diff option for overriding list of (staged) files (35fcce9)

v12.4.3

Compare Source

Bug Fixes
  • deps: downgrade yaml@1.10.2 to support Node.js 12 (383a96e)
  • deps: update commander@^9.2.0 (22ebf52)
  • deps: update yaml@^2.0.1 (ec73af0)

v12.4.2

Compare Source

Bug Fixes
  • correctly handle --max-arg-length cli option (1db5f26)

v12.4.1

Compare Source

Bug Fixes
  • correctly handle symlinked config files (b3f63ec)

v12.4.0

Compare Source

Bug Fixes
  • handle empty input by returning empty array from parseGitZOutput (a118817)
  • limit configuration discovery to cwd (d8fdf1d)
  • restore functionality of parent globs for a single configuration file (877ab4c)
Features
  • expose --max-arg-length cli option (e8291b0)

v12.3.8

Compare Source

Bug Fixes
  • avoid passing unexpected arguments from forEach to process.kill() (1b1f0e4)
  • clear execution interruption interval on first catch (46952cb)

v12.3.7

Compare Source

Bug Fixes
  • improve renderer logic for --silent and FORCE_COLOR settings (d327873)

v12.3.6

Compare Source

Bug Fixes

v12.3.5

Compare Source

Bug Fixes
  • search all configs regardless of staged files (4b605cd)

v12.3.4

Compare Source

Bug Fixes

v12.3.3

Compare Source

Bug Fixes
  • use config directory as cwd, when multiple configs present (#​1091) (9a14e92)

v12.3.2

Compare Source

Bug Fixes
  • handle symlinked .git directories (3a897ff)

v12.3.1

Compare Source

Bug Fixes
  • deps: update dependencies (f190fc3)

v12.3.0

Compare Source

Features
  • add --cwd option for overriding task directory (62b5b83)

v12.2.2

Compare Source

Bug Fixes
  • always search config from cwd first (4afcda5)

v12.2.1

Compare Source

Bug Fixes
  • only

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch 2 times, most recently from 8ead2f4 to cedfdfc Compare February 22, 2021 17:39
@renovate renovate bot changed the title chore(deps): update dependency husky to v5 chore(deps): update dependency husky to v6 Apr 26, 2021
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from cedfdfc to 02638d5 Compare April 26, 2021 14:58
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 02638d5 to 47f6f8d Compare May 9, 2021 20:25
@renovate renovate bot changed the title chore(deps): update dependency husky to v6 chore(deps): update code formatter packages (major) May 9, 2021
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 47f6f8d to ec1aaaf Compare October 18, 2021 18:29
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from ec1aaaf to d2503e0 Compare March 7, 2022 13:26
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from d2503e0 to 92dfc4e Compare March 26, 2022 15:09
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 92dfc4e to 28bb4fd Compare April 25, 2022 03:07
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 28bb4fd to a651bea Compare May 15, 2022 19:40
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from a651bea to 01cc24d Compare June 18, 2022 19:23
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 01cc24d to 897f2f4 Compare September 25, 2022 15:19
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 897f2f4 to e56a4c4 Compare November 20, 2022 15:25
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from e56a4c4 to adef4da Compare March 16, 2023 11:58
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from adef4da to b90d0ba Compare April 17, 2023 10:08
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from b90d0ba to dbce52f Compare May 28, 2023 09:54
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch 2 times, most recently from 6d3505d to 0b43b97 Compare July 2, 2023 16:44
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch 2 times, most recently from 5738599 to 65edc84 Compare July 8, 2023 16:52
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 65edc84 to adcdc9f Compare August 3, 2023 08:03
Copy link

@codeclimate codeclimate bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR diff size of 16010 lines exceeds the maximum allowed for the inline comments feature.

@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from adcdc9f to 7d51545 Compare August 13, 2023 19:18
Copy link

@codeclimate codeclimate bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR diff size of 16082 lines exceeds the maximum allowed for the inline comments feature.

@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 7d51545 to 3f5e7ca Compare August 13, 2023 21:21
Copy link

@codeclimate codeclimate bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR diff size of 16082 lines exceeds the maximum allowed for the inline comments feature.

@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 3f5e7ca to 79d4291 Compare August 15, 2023 16:40
Copy link

@codeclimate codeclimate bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR diff size of 16082 lines exceeds the maximum allowed for the inline comments feature.

@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 79d4291 to 789fae1 Compare August 21, 2023 11:35
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch 4 times, most recently from 7a45377 to 62e0c4d Compare February 5, 2024 16:38
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 62e0c4d to 0045792 Compare February 14, 2024 01:50
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 0045792 to 68f5251 Compare February 21, 2024 12:46
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch 2 times, most recently from 610f467 to 13af44b Compare March 30, 2024 01:05
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch 2 times, most recently from 9994cab to ade2c2f Compare May 25, 2024 12:07
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch 2 times, most recently from fc6fe7b to 63fcaf9 Compare June 5, 2024 10:45
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch 3 times, most recently from ba88157 to 1072748 Compare June 12, 2024 18:21
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch 4 times, most recently from 7fd7ef6 to 4a41451 Compare July 18, 2024 17:58
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch 3 times, most recently from a723159 to ca67941 Compare July 29, 2024 15:47
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from ca67941 to 3d294e4 Compare August 3, 2024 10:17
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 3d294e4 to e309cb5 Compare August 13, 2024 08:25
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch 2 times, most recently from 1852cb9 to 2a09b95 Compare August 22, 2024 10:38
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 2a09b95 to 89c7ecd Compare September 1, 2024 17:01
@renovate renovate bot force-pushed the renovate/major-code-formatter-packages branch from 89c7ecd to 7b3b1b7 Compare September 12, 2024 01:36
Copy link

codeclimate bot commented Sep 12, 2024

Code Climate has analyzed commit 7b3b1b7 and detected 0 issues on this pull request.

View more on Code Climate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants