-
Notifications
You must be signed in to change notification settings - Fork 150
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 external major (major) #539
Conversation
This PR will trigger no release when merged. |
4e1c997
to
5dfe905
Compare
5dfe905
to
74bbec3
Compare
a627fe3
to
34f3c93
Compare
34f3c93
to
bf7a3c2
Compare
bb6e0cc
to
a9556df
Compare
5f33bd3
to
39aa7ad
Compare
f1b9718
to
634f330
Compare
23f3f9f
to
b16f135
Compare
563a42c
to
125ab5a
Compare
9069cf2
to
852b79b
Compare
ea6732a
to
a0ba585
Compare
33f2071
to
1ded6cc
Compare
b1e583a
to
39471e1
Compare
39471e1
to
feb1008
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #539 +/- ##
=======================================
Coverage 99.75% 99.75%
=======================================
Files 11 11
Lines 2039 2039
=======================================
Hits 2034 2034
Misses 5 5 ☔ View full report in Codecov by Sentry. |
🎉 This PR is included in version 8.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This PR contains the following updates:
9.2.6
->10.0.2
1.3.0
->2.0.0
18.19.26
->20.11.30
8.0.1
->9.1.0
8.0.3
->9.0.11
14.0.1
->15.2.2
^3.0.0
->^4.0.0
10.0.2
->11.0.0
10.0.3
->11.0.0
21.1.2
->22.0.12
10.1.2
->11.0.4
Release Notes
semantic-release/github (@semantic-release/github)
v10.0.2
Compare Source
Bug Fixes
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
Features
BREAKING CHANGES
bcoe/c8 (c8)
v9.1.0
Compare Source
Features
Bug Fixes
v9.0.0
Compare Source
⚠ BREAKING CHANGES
Features
typicode/husky (husky)
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
~/.huskyrc
correctly (compatibility with v8)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
v9
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
v9
Further Size Reduction
v8
was already the most compact Git hooks manager at approximately6kB
.v9
takes this a step further, reducing the size to just3kB
, 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
--provenance
for safer publishing.$XDG_CONFIG_HOME
support. Move~/.huskyrc
to~/.config/husky/init.sh
for centralized configuration.husky install
. Usehusky
orhusky some/dir
for the same functionality (deprecation notice to be added)..git
is missing; it now triggers a warning instead of failure.HUSKY_DEBUG=1
withHUSKY=2
for debugging.ESM
for module usage.How to Migrate
v9
is backward compatible withv8
, allowing you to freely upgrade and migrate your hooks later.package.json
.husky/pre-commit
okonet/lint-staged (lint-staged)
v15.2.2
Compare Source
Patch Changes
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
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 thestdin
of the spawned commands has accepted input, and essentially gotten stuck waiting. Now thestdin
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
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 uselilconfig
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, usefs.realpath()
only for symlinks. It looks likefs.realpath()
changes some Windows mapped network filepaths unexpectedly, causing issues.v15.1.0
Compare Source
Minor Changes
0423311
Thanks @danielbayley! - Add support for loading configuration frompackage.yaml
andpackage.yml
files, supported bypnpm
.Patch Changes
105d901
Thanks @iiroj! - Suppress some warnings when using the "--quiet" flagv15.0.2
Compare Source
Patch Changes
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
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.0This 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.
remarkjs/remark-gfm (remark-gfm)
v4.0.0
Compare Source
Change
b8cc334
Update@types/mdast
,unified
, utilitiesmigrate: update too
9eb0f54
Change to useexports
migrate: don’t use private APIs
5715c93
Change to require Node.js 16migrate: update too
Full Changelog: remarkjs/remark-gfm@3.0.1...4.0.0
remarkjs/remark (remark-parse)
v11.0.0
Compare Source
(see
15.0.0
)semantic-release/semantic-release (semantic-release)
v22.0.12
Compare Source
Bug Fixes
v22.0.11
Compare Source
Bug Fixes
v22.0.10
Compare Source
Bug Fixes
v22.0.9
Compare Source
Bug Fixes
v22.0.8
Compare Source
Bug Fixes
v22.0.7
Compare Source
Bug Fixes
Features
v22.0.6
Compare Source
Bug Fixes
v22.0.5
Compare Source
Bug Fixes
v22.0.4
Compare Source
Bug Fixes
v22.0.3
Compare Source
Bug Fixes
exports
definition for the time being (561e2d6), closes #2968. see https://github.com/semantic-release/semantic-release/issues/2978 for more information.v22.0.2
Compare Source
Bug Fixes
v22.0.1
Compare Source
Bug Fixes
release-notes-generator
andcommit-analyzer
plugins to stable versions (041e4f7), closes #2934v22.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
v20.6.1 to avoid a known node bug
unifiedjs/unified (unified)
v11.0.4
Compare Source
Types
1ca1a43
Add TypeScript declaration mapsby @remcohaszing in https://github.com/unifiedjs/unified/pull/230
Full Changelog: unifiedjs/unified@11.0.3...11.0.4
v11.0.3
Compare Source
Fix
8dee2ab
Fix support for functions in dataFull Changelog: unifiedjs/unified@11.0.2...11.0.3
v11.0.2
Compare Source
cea788b
Fix type of settings if nothing is registered yetFull Changelog: unifiedjs/unified@11.0.1...11.0.2
v11.0.1
Compare Source
d1a915d
Fix incorrect type ofsettings
in presetsFull Changelog: unifiedjs/unified@11.0.0...11.0.1
v11.0.0
Compare Source
Change
baf80b2
Change to require Node.js 16migrate: update too
dd9834a
Update@types/unist
migrate: update too
620ccf9
Updatevfile
migrate: update too
Change (unlikey to affect you)
a44db46
AddData
,Settings
types to augment shared datamigrate: if you deal with data, type it, see commit for info
fb49556
Change to replaceBuffer
withUint8Array
migrate: you’re probably fine unless you use weird encodings, see commit for details if so
f3e71a8
RemoveAttacher
typemigrate: use
Plugin
insteadcc53bb6
RemoveFrozenProcessor
typemigrate: use
Processor
instead1aa3494
Change to yieldundefined
, notnull
migrate: expect
undefined
932c140
Change to useexports
migrate: don’t use private APIs
8e57478
Remove support for classes as compilers, parsersmigrate: if you love classes, see commit message
4676814
Remove support for compilers returning nullishmigrate: nobody did that
807ffb9
Add improved typesmigrate: it’s probably just better if anything changed at all
b35afe0
Add useful error on empty presetsby @wooorm in https://github.com/unifiedjs/unified/pull/202
6f068a0
Fix to deep clone preset settings56ee288
Fix non-first parameter merging when reconfiguring pluginsMisc
e58b095
ad06700
40f0329
Refactor code-styleffc146c
Updatetypescript
by @ChristianMurphy in https://github.com/unifiedjs/unified/pull/216
7148746
144eec0
2d95451
Add improved docsafb704a
Fix some typosby @ChristianMurphy in https://github.com/unifiedjs/unified/pull/225
2aa15ea
Refactor typesa06537c
Add sponsorFull Changelog: unifiedjs/unified@10.1.2...11.0.0
Configuration
📅 Schedule: Branch creation - "after 2pm on Monday" in timezone Europe/Zurich, 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.
This PR has been generated by Mend Renovate. View repository job log here.