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.

Sign up for GitHub

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

Jump to bottom

Chore: Update changesets monorepo [skip netlify] (major) - autoclosed #166

Closed
wants to merge 1 commit into from
Closed

Chore: Update changesets monorepo [skip netlify] (major) - autoclosed #166

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 6, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/eslint (source) 8.4.10 -> 9.6.1 age adoption passing confidence
@types/node (source) 18.11.13 -> 20.16.3 age adoption passing confidence
husky 8.0.2 -> 9.1.5 age adoption passing confidence
lint-staged 13.1.0 -> 15.2.10 age adoption passing confidence
type-fest 3.3.0 -> 4.26.0 age adoption passing confidence
typescript (source) 4.9.4 -> 5.5.4 age adoption passing confidence

Release Notes

typicode/husky (husky)

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

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

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)
sindresorhus/type-fest (type-fest)

v4.26.0

Compare Source

v4.25.0

Compare Source

v4.24.0

Compare Source

v4.23.0

Compare Source

v4.22.1

Compare Source

v4.22.0

Compare Source

v4.21.0

Compare Source

New types
Fixes
  • Jsonify: Convert undefined to null in union element of array (#​901) 60c1024
  • Exact: Fix support for Date in union (#​902) d89a709
  • CamelCasedPropertiesDeep: Fix handling of non-recursive types inside target type (#​890) 476024d

v4.20.1

Compare Source

v4.20.0

Compare Source

v4.19.0

Compare Source

v4.18.3

Compare Source

v4.18.2

Compare Source

  • CamelCasedPropertiesDeep: Fix tuple being incorrectly turned into array (#​818) 4e7bb18

v4.18.1

Compare Source

v4.18.0

Compare Source

New types
Improvements

v4.17.0

Compare Source

v4.16.0

Compare Source

New types
Fixes

v4.15.0

Compare Source

New types
Fixes

v4.14.0

Compare Source

v4.13.1

Compare Source

  • SetParameterType: Properly fix compatibility with TypeScript 5.4 (#​836) a186adb

v4.13.0

Compare Source

New types
Improvements
Fixes
  • SetParameterType: Fix compatibility with TypeScript 5.4 (#​835) 2bc451e
  • OmitDeep: Fix handling for when the given path is not matched (#​834) 4f14bff

v4.12.0

Compare Source

New types

v4.11.1

Compare Source

v4.11.0

Compare Source

New types
Improvements

v4.10.3

Compare Source

  • PartialOnUndefinedDeep: Fix it incorrectly removing non-optional properties when the input type contains an index signature (#​764) 2f4b55a

v4.10.2

Compare Source

v4.10.1

Compare Source

  • Fix support for exactOptionalPropertyTypes: true tsconfig (#​804) a54e313

v4.10.0

Compare Source

  • Get: Fix handling of readonly array (#​799) 4a38651
  • SharedUnionFieldsDeep: Skip if input type is not a union type (#​798) 6f1db93
  • DelimiterCasedPropertiesDeep: Don't recurse into intersection type that include primitive value (#​789) eb96609
  • Merge: Don't turn undefined into optional key (#​787) 0aec247

v4.9.0

Compare Source

New types
Improvements

v4.8.3

Compare Source

  • MergeDeep: Fix optional key when value type is any or never (#​777) 609c097
  • Paths: Ensure it doesn't recurse into Map or Set's prototype properties (#​772) 6759853

v4.8.2

Compare Source

  • DelimiterCasedPropertiesDeep: Fix handing of string (#​768) e26c779

v4.8.1

Compare Source

  • Jsonify: Fix usage with readonly array f8019c2
  • Revert "Add Element to type BuiltIns (#​745)" 1b25feb
    • It caused problems when DOM types are not available.

v4.8.0

Compare Source

v4.7.1

Compare Source

  • Revert "PartialDeep: Ensure it doesn't recurse into prototype properties" (#​743) 9f47b11

v4.7.0

Compare Source

New types
Improvements
  • Writable: Support array, map, and set (#​726) b9723d4
  • PartialDeep: Ensure it doesn't recurse into prototype properties (#​738) 5eeac02
  • ConditionalPickDeep: Ensure it doesn't recurse into prototype properties (#​736) 9960ba4

v4.6.0

Compare Source

New types
Fixes
Meta

v4.5.0

Compare Source

New types
Improvements

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 becomes conflicted, 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.

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Aug 6, 2024 •
edited
Loading

⚠️ No Changeset found

Latest commit: 593f79c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/dev/major-changesets-monorepo branch 3 times, most recently from f6e2b26 to a005bf6 Compare August 13, 2024 07:09
@renovate renovate bot force-pushed the renovate/dev/major-changesets-monorepo branch 5 times, most recently from fd88b99 to f1d71ea Compare August 20, 2024 13:09
@renovate renovate bot force-pushed the renovate/dev/major-changesets-monorepo branch 4 times, most recently from 6910676 to da23b07 Compare September 1, 2024 12:55
@renovate renovate bot force-pushed the renovate/dev/major-changesets-monorepo branch from da23b07 to 593f79c Compare September 1, 2024 17:10
@renovate renovate bot changed the title Chore: Update changesets monorepo [skip netlify] (major) Chore: Update changesets monorepo [skip netlify] (major) - autoclosed Sep 2, 2024
@renovate renovate bot closed this Sep 2, 2024
@renovate renovate bot deleted the renovate/dev/major-changesets-monorepo branch September 2, 2024 04:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants