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(deps): update external major (major) #33

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

chore(deps): update external major (major) #33

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 19, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@semantic-release/npm 10.0.6 -> 12.0.1 age adoption passing confidence devDependencies major
actions/checkout v3 -> v4 age adoption passing confidence action major
actions/setup-node v3 -> v4 age adoption passing confidence action major
algoliasearch ^4.17.0 -> ^5.0.0 age adoption passing confidence dependencies major
c8 7.14.0 -> 10.1.2 age adoption passing confidence devDependencies major
codecov 3.3.0 -> 4.1.0 age adoption passing confidence orb major
fetch-retry ^5.0.4 -> ^6.0.0 age adoption passing confidence dependencies major
github/codeql-action v2 -> v3 age adoption passing confidence action major
husky 8.0.3 -> 9.1.5 age adoption passing confidence devDependencies major
junit-report-builder 3.2.1 -> 5.0.0 age adoption passing confidence devDependencies major
lint-staged 13.3.0 -> 15.2.9 age adoption passing confidence devDependencies major
mime ^3.0.0 -> ^4.0.0 age adoption passing confidence dependencies major
semantic-release 21.1.2 -> 24.1.0 age adoption passing confidence devDependencies major
sinon (source) ^15.0.4 -> ^18.0.0 age adoption passing confidence devDependencies major

Release Notes

semantic-release/npm (@​semantic-release/npm)

v12.0.1

Compare Source

Bug Fixes
  • deps: update dependency execa to v9 (9ac5ed0)

v12.0.0

Compare Source

Features
  • exports: defined exports to point at ./index.js (9e193c2)
  • node-versions: dropped support for node v18 and v19 (2df962b)
BREAKING CHANGES
  • exports: exports has been defined, which prevents access to private apis (which arent
    intended for consumption anyway)
  • node-versions: node v18 and v19 are no longer supported

v11.0.3

Compare Source

Bug Fixes

even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully

v11.0.2

Compare Source

Bug Fixes
  • deps: update dependency npm to v10.2.5 (42b5dec)

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

Bug Fixes
  • deps: update dependency npm to v10 (819f257)
Features
  • node-versions: raised the minimum required node version to v18.17 and dropped v19 support (6413130)
BREAKING CHANGES
  • node-versions: node v18.17 is now the minimum required version and support for v19 has been dropped
actions/checkout (actions/checkout)

v4

Compare Source

actions/setup-node (actions/setup-node)

v4

Compare Source

algolia/algoliasearch-client-javascript (algoliasearch)

v5.1.0

Compare Source

v5.0.2

Compare Source

v5.0.0

Compare Source

New major version released! Browse our documentation

bcoe/c8 (c8)

v10.1.2

Compare Source

Bug Fixes
  • deps: make monocart-coverage-reports an optional with meta defined (3b91fda)

v10.1.1

Compare Source

Bug Fixes

v10.1.0

Compare Source

Features

v10.0.0

Compare Source

⚠ BREAKING CHANGES
  • deps: Node 18 is now the minimum supported Node.js version
Bug Fixes
  • deps: update test-exclude with new glob / minimatch (#​531) (e33cf30)

v9.1.0

Compare Source

Features
Bug Fixes
  • refactor: remove stale check for createDynamicModule (5e18365)

v9.0.0

Compare Source

⚠ BREAKING CHANGES
  • build: minimum Node.js version is now 14.14.0
Features
  • build: minimum Node.js version is now 14.14.0 (2cdc86b)
  • deps: update foreground-child to promise API (#​512) (b46b640)
  • deps: use Node.js built in rm (2cdc86b)

v8.0.1

Compare Source

Bug Fixes

v8.0.0

Compare Source

⚠ BREAKING CHANGES
  • dropped Node 10 support (#​475)
Miscellaneous Chores
jonbern/fetch-retry (fetch-retry)

v6.0.0: Permissive wrapping, fix global pollution and export types

Compare Source

Adds permissive wrapping of the fetch function while retaining the original typing of the wrapped library. This enables us to handle that there are slight variations between fetch implementations in node.

This change also removes the need for the triple-slash directive which polluted the global namespace with DOM typings. The new version also exports all the types defined in the library for good measure.

Many thanks to @​alecmev for providing an excellent PR which made these changes possible.

github/codeql-action (github/codeql-action)

v3

Compare Source

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
davidparsson/junit-report-builder (junit-report-builder)

v5.0.0

Compare Source

v4.0.1

Compare Source

v4.0.0

Compare Source

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

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.
broofa/mime (mime)

v4.0.4

Compare Source

v4.0.3

Compare Source

v4.0.2

Compare Source

v4.0.1

Compare Source

v4.0.0

Compare Source

semantic-release/semantic-release (semantic-release)

v24.1.0

Compare Source

v24.0.0

Compare Source

Bug Fixes
  • deps: upgraded to the beta of the commit-analyzer plugin (dfc3d91)
  • deps: upgraded to the beta of the release-notes-generator plugin (4a4cd92)
BREAKING CHANGES
  • deps: the commit-analyzer plugin now expects to be used with the latest major versions of
    conventional-changelog packages. if you are installing any of these packages in addition to
    semantic-release, be sure to update them as well
  • deps: the release-notes-generator plugin now expects to be used with the latest major
    versions of conventional-changelog packages. if you are installing any of these packages in addition
    to semantic-release, be sure to update them as well

v23.1.1

Compare Source

v23.1.0

Compare Source

v23.0.8

Compare Source

Bug Fixes
  • deps: rename read-pkg-up -> read-package-up (4980cba)
  • deps: rename read-pkg-up -> read-package-up (#​3249) (95a8b9e)

v23.0.7

Compare Source

v23.0.6

Compare Source

Bug Fixes

v23.0.5

Compare Source

v23.0.4

Compare Source

v23.0.3

Compare Source

v23.0.2

Compare Source

Bug Fixes

v23.0.1

Compare Source

Bug Fixes
  • deps: update dependency marked-terminal to v7 (9faded8)

v23.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES

related to https://github.com/semantic-release/semantic-release/discussions/3088

v22.0.12

Compare Source

Bug Fixes
  • Revert "fix(deps): update dependency cosmiconfig to v9" (#​3104) (f6f1bf1)

v22.0.11

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v9 (b38cd2e)

v22.0.10

Compare Source

Bug Fixes
  • revert updating cosmiconfig to v9 (88efead)

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

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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-actions
Copy link

This PR will trigger no release when merged.

@codecov
Copy link

codecov bot commented Jun 19, 2023 •
edited

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.12%. Comparing base (246192b) to head (d379e0c).
Report is 3 commits behind head on main.

❗ Current head d379e0c differs from pull request most recent head 961c4eb

Please upload reports for the commit 961c4eb to get more accurate results.

Additional details and impacted files 
@@           Coverage Diff           @@
##             main      #33   +/-   ##
=======================================
  Coverage   96.12%   96.12%           
=======================================
  Files          12       12           
  Lines        1366     1366           
=======================================
  Hits         1313     1313           
  Misses         53       53

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate-major-external-major branch from 23f1f6b to 650bc48 Compare June 28, 2023 01:20
@renovate renovate bot force-pushed the renovate-major-external-major branch from 650bc48 to 9faad3a Compare July 25, 2023 15:23
@renovate renovate bot force-pushed the renovate-major-external-major branch from 9faad3a to faba371 Compare August 5, 2023 16:44
@renovate renovate bot changed the title chore(deps): update dependency c8 to v8 chore(deps): update external major (major) Aug 13, 2023
@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from a929116 to 6c3bc82 Compare August 19, 2023 15:29
@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from 2b61ebc to 2539bc1 Compare August 26, 2023 15:35
@renovate renovate bot force-pushed the renovate-major-external-major branch from 2539bc1 to 6ce2324 Compare September 4, 2023 13:18
@renovate renovate bot force-pushed the renovate-major-external-major branch 5 times, most recently from da5d8c8 to 2046929 Compare September 16, 2023 21:35
@renovate renovate bot force-pushed the renovate-major-external-major branch 4 times, most recently from a800c1b to aab2eff Compare September 24, 2023 17:07
@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from 03b753e to 2364b3d Compare October 14, 2023 16:02
@renovate renovate bot force-pushed the renovate-major-external-major branch 4 times, most recently from c41ba36 to adb9c12 Compare October 20, 2023 16:22
@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from 58ba21f to 555ad3f Compare October 28, 2023 19:26
@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from 6a91fa5 to 81fd70e Compare November 2, 2023 22:33
@renovate renovate bot force-pushed the renovate-major-external-major branch from a36aa94 to 44c3150 Compare April 27, 2024 17:05
@renovate renovate bot force-pushed the renovate-major-external-major branch 3 times, most recently from db5386e to bea02f4 Compare May 15, 2024 21:08
@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from 62665c7 to bf16471 Compare May 25, 2024 12:32
@renovate renovate bot force-pushed the renovate-major-external-major branch from bf16471 to f745ef6 Compare June 1, 2024 03:17
@renovate renovate bot force-pushed the renovate-major-external-major branch 5 times, most recently from 1cc14ea to 961c4eb Compare June 13, 2024 00:48
@renovate renovate bot force-pushed the renovate-major-external-major branch 5 times, most recently from 4c8bbaa to a95f247 Compare July 21, 2024 00:17
@renovate renovate bot force-pushed the renovate-major-external-major branch 6 times, most recently from 03de8a3 to e124d95 Compare August 1, 2024 10:39
@renovate renovate bot force-pushed the renovate-major-external-major branch from e124d95 to e9b01d4 Compare August 3, 2024 10:02
@renovate renovate bot force-pushed the renovate-major-external-major branch 4 times, most recently from 8e807aa to 58ed523 Compare August 17, 2024 12:39
@renovate renovate bot force-pushed the renovate-major-external-major branch from 58ed523 to 1f5d9e1 Compare August 20, 2024 15:08
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.

None yet
0 participants