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 all non-major dependencies #38

Open

renovate wants to merge 1 commit into main from renovate/all-minor-patch

Contributor

renovate bot commented Dec 2, 2024 •

edited

Loading

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@commitlint/cli (source)	`^19.3.0` -> `^19.7.1`					devDependencies	minor
@commitlint/config-conventional (source)	`^19.2.2` -> `^19.7.1`					devDependencies	minor
go (source)	`1.21` -> `1.23.6`					golang	minor
husky	`^9.0.11` -> `^9.1.7`					devDependencies	minor
lint-staged	`^15.2.2` -> `^15.4.3`					devDependencies	minor

Release Notes

conventional-changelog/commitlint (@commitlint/cli)

`v19.7.1`

Note: Version bump only for package @commitlint/cli

`v19.6.1`

Note: Version bump only for package @commitlint/cli

`v19.6.0`

Note: Version bump only for package @commitlint/cli

`v19.5.0`

Features

cli: use special errorCode for missing rules/config #4142 (#4143) (d7070d8)

19.4.1 (2024-08-28)

Note: Version bump only for package @commitlint/cli

`v19.4.1`

Note: Version bump only for package @commitlint/cli

`v19.4.0`

Features

support command line options from a file (#4109) (a20e890)
support linting from the last tag (#4110) (4b204ec)

conventional-changelog/commitlint (@commitlint/config-conventional)

`v19.7.1`

Note: Version bump only for package @commitlint/config-conventional

`v19.6.0`

Note: Version bump only for package @commitlint/config-conventional

`v19.5.0`

Note: Version bump only for package @commitlint/config-conventional

19.4.1 (2024-08-28)

Note: Version bump only for package @commitlint/config-conventional

19.2.2 (2024-04-14)

Note: Version bump only for package @commitlint/config-conventional

`v19.4.1`

Note: Version bump only for package @commitlint/config-conventional

golang/go (go)

`v1.23.6`

`v1.23.5`

`v1.23.4`

`v1.23.3`

`v1.23.2`

`v1.23.1`

`v1.23.0`

`v1.22.12`

`v1.22.11`

`v1.22.10`

`v1.22.9`

`v1.22.8`

`v1.22.7`

`v1.22.6`

`v1.22.5`

`v1.22.4`

`v1.22.3`

`v1.22.2`

`v1.22.1`

`v1.22.0`

`v1.21.13`

`v1.21.12`

`v1.21.11`

`v1.21.10`

`v1.21.9`

`v1.21.8`

`v1.21.7`

`v1.21.6`

`v1.21.5`

`v1.21.4`

`v1.21.3`

`v1.21.2`

`v1.21.1`

typicode/husky (husky)

`v9.1.7`

`v9.1.6`

`v9.1.5`

`v9.1.4`

`v9.1.3`

fix: better handle space in PATH

`v9.1.2`

`v9.1.1`

`v9.1.0`

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 😉

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

`v15.4.3`

Patch Changes

#1512 cbfed1d Thanks @tarik02! - Adjust TypeScript types for the default export so that it can be used as a value without error TS2693.

`v15.4.2`

Patch Changes

#1509 8827ebf Thanks @iiroj! - Change lint-staged's dependencies to use caret (^) ranges instead of tilde (~). This makes it easier for package managers to perform dependency management when minor-level updates are also permitted instead of just patch-level.

`v15.4.1`

Patch Changes

#1504 1c7a45e Thanks @iiroj! - Default TypeScript config filenames match JS equivalents.
#1504 9cc18c9 Thanks @iiroj! - Add missing conditional exports syntax for TypeScript types.

`v15.4.0`

Minor Changes

#1500 a8ec1dd Thanks @iiroj! - Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files:
```
/**
 * @&#8203;filename: lint-staged.config.js
 * @&#8203;type {import('lint-staged').Configuration}
 */
export default {
  '*': 'prettier --write',
}
```
It's also possible to use the .ts file extension for the configuration if your Node.js version supports it. The --experimental-strip-types flag was introduced in Node.js v22.6.0 and unflagged in v23.6.0, enabling Node.js to execute TypeScript files without additional configuration.
```
export NODE_OPTIONS="--experimental-strip-types"

npx lint-staged --config lint-staged.config.ts
```

Patch Changes

#1501 9b79364 Thanks @iiroj! - Handle possible failures when logging user shell for debug info.

`v15.3.0`

Minor Changes

#1495 e69da9e Thanks @iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.
#1493 fa0fe98 Thanks @iiroj! - Added more help messages around the automatic git stash that lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.

For example:
```
% npx lint-staged
✔ Backed up original state in git stash (20addf8)
✔ Running tasks for staged files...
✔ Applying modifications from tasks...
✔ Cleaning up temporary files...
```
where the backup can be seen with git show 20addf8, or git stash list:
```
% git stash list
stash@{0}: lint-staged automatic backup (20addf8)
```

`v15.2.11`

Patch Changes

#1484 bcfe309 Thanks @wormsik! - Escape paths containing spaces when using the "shell" option.
#1487 7dd8caa Thanks @iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.

`v15.2.10`

Patch Changes

#1471 e3f283b Thanks @iiroj! - Update minor dependencies, including micromatch@~4.0.8.

`v15.2.9`

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`

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`

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`

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`

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`

Patch Changes

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

Configuration

📅 Schedule: Branch creation - "before 2am on Monday" in timezone Europe/Berlin, 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.

renovate bot added the dependencies label

renovate bot requested a review from mheob as a code owner

December 2, 2024 00:31

height bot commented Dec 2, 2024

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

coderabbitai bot commented Dec 2, 2024 •

edited

Loading

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @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.
- @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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 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 for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from f6d5191 to 7913c4e Compare

December 10, 2024 15:19

renovate bot force-pushed the renovate/all-minor-patch branch from 7913c4e to 2c7e140 Compare

December 15, 2024 16:10

renovate bot force-pushed the renovate/all-minor-patch branch from 2c7e140 to 03549b5 Compare

December 28, 2024 11:17

renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from b5982ae to 629f571 Compare

January 17, 2025 05:56

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 7de2923 to 45780d5 Compare

January 26, 2025 16:35

renovate bot force-pushed the renovate/all-minor-patch branch from 45780d5 to 1bab811 Compare

February 2, 2025 13:43


          chore(deps): update all non-major dependencies

662c9c6

renovate bot force-pushed the renovate/all-minor-patch branch from 1bab811 to 662c9c6 Compare

February 4, 2025 17:17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels