fix(deps): update all non major npm update #326
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-non-major-npm-update
branch
2 times, most recently
from
cbc0b40 to
10b0429
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-non-major-npm-update
branch
2 times, most recently
from
093ec74 to
9af2c42
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-non-major-npm-update
branch
2 times, most recently
from
10c0ee6 to
dd41af1
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-non-major-npm-update
branch
3 times, most recently
from
b970002 to
4ac5cd8
Compare
renovate
bot
force-pushed
the
renovate/all-non-major-npm-update
branch
3 times, most recently
from
1e52709 to
f63d678
Compare
renovate
bot
force-pushed
the
renovate/all-non-major-npm-update
branch
from
f63d678 to
9a7e305
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^9.27.0->^9.29.0^22.15.24->^22.15.32^8.33.0->^8.34.1^8.33.0->^8.34.1^1.9.0->^1.10.0^9.27.0->^9.29.0^4.0.2->^4.0.3^16.1.0->^16.1.2^29.3.4->^29.4.0Release Notes
eslint/eslint (@eslint/js)
v9.29.0Compare Source
v9.28.0Compare Source
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.34.1Compare Source
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.34.0Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.33.1Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.34.1Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.34.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.33.1Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
axios/axios (axios)
v1.10.0Compare Source
Bug Fixes
Features
Contributors to this release
eslint/eslint (eslint)
v9.29.0Compare Source
v9.28.0Compare Source
form-data/form-data (form-data)
v4.0.3Compare Source
lint-staged/lint-staged (lint-staged)
v16.1.2Compare Source
Patch Changes
#1570
a7c0c88Thanks @ItsNickBarry! - When using--diff-filterwith theDoption to include deleted staged files, lint-staged no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error fromgit addlikefatal: pathspec 'deleted-file' did not match any files.38f942eThanks @iiroj! - Removed an extraneous log entry that printedshouldHidePArtiallyStagedFilesto console output.v16.1.1Compare Source
Patch Changes
#1565
3686977Thanks @iiroj! - Lint-staged now explicitly warns about potential data loss when using--no-stash.#1571
02299a9Thanks @iiroj! - Function tasks (introduced in v16.0.0) only received the staged files matching the conpmnfigured glob, instead of all staged files.#1563
bc61c74Thanks @iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the--no-stashoption. This happened because--no-stashimplied--no-hide-partially-staged, meaning unstaged changes to files which also had other staged changes were added to the commit by lint-staged; this is no longer the case.The previous (incorrect) behavior can still be achieved by using both options
--no-stash --no-hide-partially-stagedat the same time.kulshekhar/ts-jest (ts-jest)
v29.4.0Compare Source
Features
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.
This PR was generated by Mend Renovate. View the repository job log.