fix(deps): update minor updates (minor) #28
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=80&v=4){kind=small}
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
|
Thank you for following the naming conventions! 🙏 |
✅ Deploy Preview for ai-models-table ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
renovate
bot
force-pushed
the
renovate/minor-updates
branch
5 times, most recently
from
b18523a to
dac1be4
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
7 times, most recently
from
e9d9cb7 to
3bcd245
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
7 times, most recently
from
4b7d160 to
be59e10
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
6 times, most recently
from
44c0858 to
462180d
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
5 times, most recently
from
886c1b3 to
02306fd
Compare
renovate
bot
force-pushed
the
renovate/minor-updates
branch
from
02306fd to
3b5a005
Compare
Signed-off-by: Renovate Bot <bot@renovateapp.com>
renovate
bot
force-pushed
the
renovate/minor-updates
branch
from
3b5a005 to
bd02fef
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:
16.2.23->16.3.3^16.2.23->^16.3.31.5.0->1.6.0^1.5.0->^1.6.1^1.5.0->^1.6.0^1.63.0->^1.73.0^16.1.5->^16.2.410.14.0->10.18.3^1.260.1->^1.275.20.6.14->0.7.0^9.8.1->^9.11.1^7.62.0->^7.65.0^1.3.6->^1.4.0^4.3.0->^4.5.0^4.0.17->^4.1.12Release Notes
anolilab/javascript-style-guide (@anolilab/eslint-config)
v16.3.3Compare Source
Bug Fixes
v16.3.2Compare Source
Bug Fixes
v16.3.1Compare Source
Bug Fixes
v16.3.0Compare Source
Features
Bug Fixes
v16.2.26Compare Source
Bug Fixes
v16.2.25Compare Source
Bug Fixes
v16.2.24Compare Source
Bug Fixes
c15t/c15t (@c15t/backend)
v1.6.0Compare Source
Minor Changes
84ab0c7: For a full detailed changelog see the v1.6.0 release notes.Patch Changes
84ab0c7]c15t/c15t (@c15t/react)
v1.6.1Compare Source
Patch Changes
6257a20: fix(react): dialog scroll lock persisting after closurev1.6.0Compare Source
Minor Changes
84ab0c7: For a full detailed changelog see the v1.6.0 release notes.Patch Changes
84ab0c7]c15t/c15t (@c15t/translations)
v1.6.0Compare Source
Minor Changes
84ab0c7: For a full detailed changelog see the v1.6.0 release notes.lobehub/lobe-icons (@lobehub/icons-static-svg)
v1.73.0Compare Source
Released on 2025-02-15
✨ Features
💄 Styles
Improvements and Fixes
What's improved
Styles
v1.72.0Compare Source
Released on 2025-02-15
✨ Features
Improvements and Fixes
What's improved
v1.71.0Compare Source
Released on 2025-02-14
✨ Features
💄 Styles
Improvements and Fixes
What's improved
Styles
v1.70.0Compare Source
Released on 2025-02-14
✨ Features
💄 Styles
Improvements and Fixes
What's improved
Styles
v1.69.1Compare Source
Version 1.69.1
Released on 2025-10-07
💄 Styles
Improvements and Fixes
Styles
v1.69.0Compare Source
Released on 2025-02-11
✨ Features
Improvements and Fixes
What's improved
v1.68.0Compare Source
Released on 2025-02-04
✨ Features
💄 Styles
Improvements and Fixes
What's improved
Styles
v1.67.0Compare Source
Released on 2025-02-04
✨ Features
Improvements and Fixes
What's improved
v1.66.0Compare Source
Released on 2025-02-04
✨ Features
Improvements and Fixes
What's improved
Version 1.65.1
Released on 2025-02-04
💄 Styles
360zhinao2-o1&MiniMax-Text-01.Improvements and Fixes
Styles
360zhinao2-o1&MiniMax-Text-01, closes #67 (83a87be)v1.65.0Compare Source
Released on 2025-02-03
✨ Features
Improvements and Fixes
What's improved
v1.64.0Compare Source
Released on 2025-01-28
✨ Features
Improvements and Fixes
What's improved
lint-staged/lint-staged (lint-staged)
v16.2.4Compare Source
Patch Changes
#1682
0176038Thanks @iiroj! - Update dependencies, includingnano-spawn@2.0.0with bug fixes.#1671
581a54eThanks @iiroj! - Speed up execution by only importing theyamldepedency if using YAML configuration files.v16.2.3Compare Source
Patch Changes
27cd541Thanks @iiroj! - When using--fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to make lint-staged fail.v16.2.2Compare Source
Patch Changes
#1667
699f95dThanks @iiroj! - The backup stash will not be dropped when using--fail-on-changesand there are errors. When reverting to original state is disabled (via--no-revertor--fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:
v16.2.1Compare Source
Patch Changes
#1664
8277b3bThanks @iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions isreadonly string[]and can't be mutated. Thanks @outslept!export default { --- "*": (files: string[]) => void console.log('staged files', files) +++ "*": (files: readonly string[]) => void console.log('staged files', files) }#1654
70b9af3Thanks @iiroj! - This version has been published from GitHub Actions using Trusted Publishing for npm packages.#1659
4996817Thanks @iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there arepackage.jsonfiles in the working directory. This situation might happen when running lint-staged for a single package in a monorepo.#1654
7021f0aThanks @iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates to lint-staged. This was changed in 16.2.0 after the vulnerability issues withchalkanddebug, which were also removed in the same version.Given the recent vulnerabilities in the npm ecosystem, it's best to be very careful when updating dependencies.
v16.2.0Compare Source
Minor Changes
#1615
99eb742Thanks @iiroj! - Added a new option--fail-on-changesto make lint-staged exit with code 1 when tasks modify any files, making theprecommithook fail. This is similar to thegit diff --exit-codeoption. Using this flag also implies the--no-revertflag which means any changes made my tasks will be left in the working tree after failing, so that they can be manually staged and the commit tried again.#1611
cd05fd3Thanks @rlorenzo! - Added a new option--continue-on-errorso that lint-staged will run all tasks to completion even if some of them fail. By default, lint-staded will exit early on the first failure.#1637
82fcc07Thanks @iiroj! - Internal lint-staged errors are now thrown and visible in the console output. Previously they were caught with the process exit code set to 1, but not logged. This happens when, for example, there's a syntax error in the lint-staged configuration file.#1647
a5ecc06Thanks @iiroj! - Remove debug as a dependency due to recent malware issue; read more at debug-js/debug#1005. Because of this, theDEBUGenvironment variable is no longer supported — use the--debugto enable debugging#1636
8db2717Thanks @iiroj! - Added a new option--hide-unstagedso that lint-staged will hide all unstaged changes to tracked files before running tasks. The changes will be applied back after running the tasks. Note that the combination of flags--hide-unstaged --no-hide-partially-stagedisn't meaningful and behaves the same as just--hide-unstaged.Thanks to @ItsNickBarry for the idea and initial implementation in #1552.
#1648
7900b3bThanks @iiroj! - Remove lilconfig to reduce reliance on third-party dependencies. It was used to find possible config files outside of those tracked in Git, including from the parent directories. This behavior has been moved directly into lint-staged and should work about the same.Patch Changes
#1633
7f9e485Thanks @dependabot! - Bumps listr2 from 9.0.3 to 9.0.4.#1626
99d5a9bThanks @iiroj! - Due to recent phishing attacks, for example chalk@5.6.1 was released with malware. To avoid lint-staged's users being at risk the direct dependencies are pinned to exact versions, instead of allowing future patch versions with the caret (^) range.#1588
035bbf2Thanks @outslept! - Increase performance by listing staged files and searching for configuration concurrently.#1645
deba3adThanks @iiroj! - Remove chalk as a dependency due to recent malware issue; read more at chalk/chalk#656.If you are having trouble with ANSI color codes when using lint-staged, you can try setting either
FORCE_COLOR=trueorNO_COLOR=trueenv variables.v16.1.6Compare Source
Patch Changes
e93578eThanks @iiroj! - Try to improve terminating of subprocess of tasks by usingSIGKILL, and only callingpidtreewhen the the main task process has a known pid.pnpm/pnpm (pnpm)
v10.18.3Compare Source
Patch Changes
verifyDepsBeforeInstall: installand pre/post install scripts that called other pnpm scripts #10060.@scope:registry) being parsed as property paths inpnpm config getwhen--location=projectis used #9362.pnpm config set --location=projectincorrectly handling keys with slashes (auth tokens, registry settings) #9884.pnpm-workspace.yamland.npmrcexist,pnpm config set --location=projectnow writes topnpm-workspace.yaml(matching read priority) #10072.pnpm outdated --long#10040.v10.18.2Compare Source
Patch Changes
pnpm outdated --longshould work #10040.pnpm dlxshould request the full metadata of packages, whenminimumReleaseAgeis set #9963.EPIPEerrors when piping output to other commands #10027.v10.18.1Compare Source
Patch Changes
--lockfile-onlyis used #8320.pnpm setupcreates a command shim to the pnpm executable. This is needed to be able to runpnpm self-updateon Windows #5700.pnpm install, pnpm produced false positive warnings for "skip adding to the default catalog because it already exists". This warning now only prints when usingpnpm add --save-catalogas originally intended.v10.18.0Compare Source
Minor Changes
Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.
Added configuration options for warning thresholds:
fetchWarnTimeoutMsandfetchMinSpeedKiBps.Warning messages are displayed when requests exceed time thresholds or fall below speed minimums
Related PR: #10025.
Patch Changes
minimumReleaseAgeconfiguration #10030.cleanupUnusedCatalogsconfiguration when removing dependent packages.scriptShellis set tofalse#8748.pnpm dlxshould not fail whenminimumReleaseAgeis set #10037.v10.17.1Compare Source
Patch Changes
minimumReleaseAgesetting, print this information out in the error message #9974.state.jsoncreation path when executingpnpm patchin a workspace project #9733.minimumReleaseAgeis set and thelatesttag is not mature enough, prefer a non-deprecated version as the newlatest#9987.v10.17.0Compare Source
Minor Changes
The
minimumReleaseAgeExcludesetting now supports patterns. For instance:Related PR: #9984.
Patch Changes
minimumReleaseAgecheck, when the package is requested by exact version and the packument is loaded from cache #9978.minimumReleaseAgeis set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #9979.v10.16.1Compare Source
Patch Changes
v10.16.0Compare Source
Minor Changes
There have been several incidents recently where popular packages were successfully attacked. To reduce the risk of installing a compromised version, we are introducing a new setting that delays the installation of newly released dependencies. In most cases, such attacks are discovered quickly and the malicious versions are removed from the registry within an hour.
The new setting is called
minimumReleaseAge. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, settingminimumReleaseAge: 1440ensures that only packages released at least one day ago can be installed.If you set
minimumReleaseAgebut need to disable this restriction for certain dependencies, you can list them under theminimumReleaseAgeExcludesetting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:Related issue: #9921.
Added support for
finders#9946.In the past,
pnpm listandpnpm whycould only search for dependencies by name (and optionally version). For example:prints the chain of dependencies to any installed instance of
minimist:What if we want to search by other properties of a dependency, not just its name? For instance, find all packages that have
react@17in their peer dependencies?This is now possible with "finder functions". Finder functions can be declared in
.pnpmfile.cjsand invoked with the--find-by=<function name>flag when runningpnpm listorpnpm why.Let's say we want to find any dependencies that have React 17 in peer dependencies. We can add this finder to our
.pnpmfile.cjs:Now we can use this finder function by running:
pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.
It is also possible to print out some additional information in the output by returning a string from the finder. For example, with the following finder:
Every matched package will also print out the license from its
package.json:Patch Changes
nodeVersionis not set to an exact semver version #9934.pnpm publishshould be able to publish a.tar.gzfile #9927.pnpm runreturn a non-zero exit code #9626.v10.15.1Compare Source
Patch Changes
.pnp.cjscrash when importing subpath #9904.v10.15.0Compare Source
Minor Changes
cleanupUnusedCatalogsconfiguration. When set totrue, pnpm will remove unused catalog entries during installation #9793.@*/pnpm-plugin-*#9780.pnpm config getnow prints an INI string for an object value #9797.pnpm config getnow accepts property paths (e.g.pnpm config get catalog.react,pnpm config get .catalog.react,pnpm config get 'packageExtensions["@​babel/parser"].peerDependencies["@​babel/types"]'), andpnpm config setnow accepts dot-leading or subscripted keys (e.g.pnpm config set .ignoreScripts true).pnpm config get --jsonnow prints a JSON serialization of config value, andpnpm config set --jsonnow parses the input value as JSON.Patch Changes
pnpm createcommand, must verify whether the node version is supported even if a cache already exists #9775.*/*to theAcceptheader to avoid getting a 406 error on AWS CodeArtifact #9862.pnpm dlx pkg --helpdoesn't pass--helptopkg#9823.PostHog/posthog-js (posthog-js)
v1.275.2Compare Source
1.275.2
Patch Changes
#2431
7d45a7aThanks @marandaneto! - fix: remove deprecated attribute $exception_personURL from exception eventsUpdated dependencies [
daf919b,7d45a7a]:v1.275.1Compare Source
1.275.1
Patch Changes
4e15fdaThanks @pauldambra! - fix: possible memory leak in session id replacement in cookieless modev1.275.0Compare Source
1.275.0
Minor Changes
ae941c2Thanks @thmsobrmlr! - Apply $current_url masking in web vitals and heatmaps extensions.v1.274.3Compare Source
1.274.3
Patch Changes
2d4eac4Thanks @pauldambra! - fix: another small potential memory leak in the recorder wrapping code"v1.274.2Compare Source
1.274.2
Patch Changes
43b8029Thanks @pauldambra! - fix: potential source of memory leak in recorder mutation throttlerv1.274.1Compare Source
1.274.1
Patch Changes
10da2ee]:v1.274.0Compare Source
1.274.0
Minor Changes
39ace01Thanks @pauldambra! - feat: remove eager loaded replay and reduce bundle size by 14.8%Patch Changes
e19a384]:v1.273.1Compare Source
1.273.1
Patch Changes
25a8846Thanks @pauldambra! - fix: rely on 'state' less when reporting replay statusv1.273.0Compare Source
1.273.0
Minor Changes
66b12f8Thanks @thmsobrmlr! - Fixes an issue where the event queue was not started until a page reload after callingopt_in_capturing()v1.272.1Compare Source
1.272.1
Patch Changes
4a39a10Thanks @pauldambra! - fix: increase max depth for app state diffingv1.272.0Compare Source
1.272.0
Minor Changes
cdfbd6dThanks @pauldambra! - fix: sConfiguration
📅 Schedule: Branch creation - "after 10:00 before 19:00 every weekday except after 13:00 before 14:00" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.