chore(deps): update all non-major dependencies #701
Merged
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
✅ Deploy Preview for friendly-lamington-fb5690 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
16 times, most recently
from
6eb2e07 to
1cb2e0b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
10 times, most recently
from
3e7937b to
ec8763b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
24 times, most recently
from
f22cbba to
cf84fac
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #701 +/- ##
=======================================
Coverage 47.39% 47.39%
=======================================
Files 11 11
Lines 671 671
Branches 34 34
=======================================
Hits 318 318
Misses 353 353 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
cf84fac to
d1eaed6
Compare
danielroe
approved these changes
Mar 20, 2025
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:
8.4.3->8.5.122.13.5->22.13.1010.0.3->10.1.01.1.0->1.2.015.4.3->15.5.01.50.1->1.51.110.4.1->10.6.55.7.3->5.8.23.3.1->3.5.02.2.4->2.2.8Release Notes
ionic-team/ionic-framework (@ionic/core)
v8.5.1Compare Source
Bug Fixes
Performance Improvements
v8.5.0Compare Source
Bug Fixes
Features
8.4.5 (2025-03-13)
Bug Fixes
8.4.4 (2025-03-13)
Bug Fixes
8.4.3 (2025-01-29)
Bug Fixes
8.4.2 (2025-01-22)
Bug Fixes
componentDidLoad()callback (#30060) (000f553), closes #300008.4.1 (2024-11-27)
Bug Fixes
v8.4.6Compare Source
Bug Fixes
v8.4.5Compare Source
Bug Fixes
v8.4.4Compare Source
Bug Fixes
antfu-collective/bumpp (bumpp)
v10.1.0Compare Source
🚀 Features
View changes on GitHub
mmkal/expect-type (expect-type)
v1.2.0Compare Source
What's Changed
❗
toMatchTypeOfis now deprecated. There are no plans to remove it any time soon, so it's not critical to immediately remove usages, but if you want to avoid squigglies in IDEs complaining about deprecations, here's what you should do:If you have an assertion like this:
There are a few options for upgrading it. The easiest is
toExtendwhich is identical to the behaviour oftoMatchTypeOf:This will work in all cases. But, there is now a stricter option that will work in many cases and be slightly more likely to catch things like
readonlyproperties matching:But, as the name suggests, this will only work on plain object types, it will fail for union types, and some other complex types.
If you have code like this:
You'll need to use
typeofbecausetoExtendandtoMatchObjectTypedo not accept argumentsFull Changelog: mmkal/expect-type@v1.1.0...v1.2.0
lint-staged/lint-staged (lint-staged)
v15.5.0Compare Source
Minor Changes
630af5fThanks @iiroj! - Lint-staged no longer resets to the original state when preventing an empty git commit. This happens when your configured tasks reset all the staged changes, typically when trying to commit formatting changes which conflict with your linter setup like ESLint or Prettier.Example with Prettier
By default Prettier prefers double quotes.
Previously
file.jswith only double quotes"changed to'git commit -am "I don't like double quotes"prettier --write file.js, converting all the'back to"'are stagedNow
file.jswith only double-quotes"changed to'git commit -am "I don't like double quotes"prettier --write file.js, converting all the'back to"microsoft/playwright (playwright-core)
v1.51.1Compare Source
Highlights
https://github.com/microsoft/playwright/issues/35093 - [Regression]: TimeoutOverflowWarning:
2149630.634 does not fit into a 32-bit signed integerhttps://github.com/microsoft/playwright/issues/35138 - [Regression]: TypeError: Cannot read properties of undefined (reading 'expectInfo')
Browser Versions
This version was also tested against the following stable channels:
v1.51.0Compare Source
pnpm/pnpm (pnpm)
v10.6.5Compare Source
v10.6.4: pnpm 10.6.4Compare Source
Patch Changes
pnpm dlxwith--allow-buildflag #9263.use-node-versionshould not cause pnpm itself to break #9276.Platinum Sponsors
Gold Sponsors
v10.6.3Compare Source
Patch Changes
pnpm install --prod=falseshould not crash, when executed in a project with apnpm-workspace.yamlfile #9233. This fixes regression introduced via #9211.Add the missing
node-optionsconfig torecursive run#9180.Removed a branching code path that only executed when
dedupe-peer-dependents=false. We believe this internal refactor will not result in behavior changes, but we expect it to make future pnpm versions behave more consistently for projects that overridededupe-peer-dependentsto false. There should be less unique bugs from turning offdedupe-peer-dependents.See details in #9259.
v10.6.2Compare Source
Patch Changes
pnpm self-updateshould always update the version in thepackageManagerfield ofpackage.json.pnpm patch-commitwill now use the same filesystem as the store directory to compare and create patch files.--loglevel=erroris used.peerDependencyRulesshould be set inpnpm-workspace.yamlto take effect.v10.6.1Compare Source
Patch Changes
--silentreporting is used.--loglevelis set toerror, don't show installation summary, execution time, and big tarball download progress.package.json#9226.approve-buildscommand, if package.json containsonlyBuiltDependenciesorignoredBuiltDependencies, the selected dependency package will continue to be written intopackage.json.v10.6.0Compare Source
Minor Changes
pnpm-workspace.yamlcan now hold all the settings that.npmrcaccepts. The settings should use camelCase #9211.pnpm-workspace.yamlexample:Projects using a
file:dependency on a local tarball file (i.e..tgz,.tar.gz,.tar) will see a performance improvement during installation. Previously, using afile:dependency on a tarball caused the lockfile resolution step to always run. The lockfile will now be considered up-to-date if the tarball is unchanged.Patch Changes
pnpm self-updateshould not leave a directory with a broken pnpm installation if the installation fails.fast-globreplace withtinyglobbyto reduce the size of the pnpm CLI dependencies #9169.pnpm deployshould not remove fields from the deployed package'spackage.jsonfile #9215.pnpm self-updateshould not read the pnpm settings from thepackage.jsonfile in the current working directory.pnpm deploycreating apackage.jsonwithout theimportsandlicensefield #9193.pnpm update -ishould list only packages that have newer versions #9206.catalogssection of thepnpm-lock.yamlfile to be removed whendedupe-peer-dependents=falseon a filtered install. #9112v10.5.2Compare Source
Patch Changes
pnpm config setcommand should change the global.npmrcfile by default.This was a regression introduced by #9151 and shipped in pnpm v10.5.0.
v10.5.1Compare Source
Patch Changes
pnpm-workspaces.yamlorpnpm-workspaces.ymlfile is found instead of apnpm-workspace.yaml#9170.pnpm-workspace.yamlby thepnpm approve-buildscommand #9168.package.json#9163overridesinpnpm-workspace.yamlshould work.pnpm dlxshould ignore settings from thepackage.jsonfile in the current working directory #9178.v10.5.0Compare Source
Minor Changes
Allow to set the "pnpm" settings from
package.jsonvia thepnpm-workspace.yamlfile #9121.Added support for automatically syncing files of injected workspace packages after
pnpm run#9081. Use thesync-injected-deps-after-scriptssetting to specify which scripts build the workspace package. This tells pnpm when syncing is needed. The setting should be defined in a.npmrcfile at the root of the workspace. Example:The
packagesfield inpnpm-workspace.yamlbecame optional.Patch Changes
pnpm linkwith no parameters should work as if--globalis specified #9151.--config.prefix such as--@​scope:registry=https://scope.example.com/npm#9089.pnpm link <path>should calculate relative path from the root of the workspace directory #9132.pnpm-lock.yamlfile when using--fix-lockfileand--filter. #8639microsoft/TypeScript (typescript)
v5.8.2Compare Source
unjs/unbuild (unbuild)
v3.5.0Compare Source
compare changes
🚀 Enhancements
fix-dts-default-cjs-exportsto transform cjs types (#513)🏡 Chore
❤️ Contributors
v3.4.2Compare Source
compare changes
🏡 Chore
❤️ Contributors
v3.4.1Compare Source
compare changes
🩹 Fixes
❤️ Contributors
v3.4.0Compare Source
compare changes
🚀 Enhancements
publishConfigfrompackage.jsonwhen defined (#506)🩹 Fixes
compositeintsconfig.json(#504)📦 Build
🏡 Chore
JavaScriptcase in pkg description (#493)❤️ Contributors
vuejs/language-tools (vue-tsc)
v2.2.8Compare Source
Bug Fixes
v-modelvariable against model type"v2.2.6Compare Source
Features
defineModel's leading comments (#5211) - Thanks to @KazariEX!Bug Fixes
defineModeloptions to collectdefaultvalue (#5209) - Thanks to @KazariEX!defineExpose's codes - Thanks to @KazariEX!defineModel(#5213) - Thanks to @KazariEX!v-modelvariable against model type (#5214) - Thanks to @KazariEX!Other Changes
can't reproducelabel - Thanks to @KazariEX!linkedCodeMappingsoffsets (#5220) - Thanks to @KazariEX!Configuration
📅 Schedule: Branch creation - "on Monday" (UTC), 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.