chore(deps): update all non-major dependencies #297
Merged
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #297 +/- ##
=======================================
Coverage 99.38% 99.38%
=======================================
Files 17 17
Lines 2272 2272
Branches 138 138
=======================================
Hits 2258 2258
Misses 14 14 Continue to review full report in Codecov by Sentry.
|
cu-infra-svc-git
force-pushed
the
renovate/all-minor-patch
branch
from
adc2764 to
32967f2
Compare
Signed-off-by: github-actions <[email protected]>
ahammond
approved these changes
Nov 4, 2024
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:
^29.5.12->^29.5.14^3.6.1->^3.6.3^2.29.1->^2.31.0^5.1.3->^5.2.1^1.100.0->^1.104.0^1.100.0->^1.104.09.1.2->9.12.3^3.3.2->^3.3.3^7.6.2->^7.6.3^29.1.5->^29.2.5^5.5.2->^5.6.3Release Notes
import-js/eslint-import-resolver-typescript (eslint-import-resolver-typescript)
v3.6.3Compare Source
Patch Changes
#305
f8d7b82Thanks @SukkaW! - Fix resolve fornode:test,node:sea, andnode:sqlitewithout sacrificing installation size#288
a4c6c78Thanks @SunsetTechuila! - fix: ignore bun built-in modulesimport-js/eslint-plugin-import (eslint-plugin-import)
v2.31.0Compare Source
Added
order]: allow validating named imports ([#3043], thanks [@manuth])extensions]: add thecheckTypeImportsoption ([#2817], thanks [@phryneas])Fixed
ExportMap/ flat config: includelanguageOptionsin context ([#3052], thanks [@michaelfaith])no-named-as-default]: Allow using an identifier if the export is both a named and a default export ([#3032], thanks [@akwodkiewicz])export]: False positive for exported overloaded functions in TS ([#3065], thanks [@liuxingbaoyu])exportMap: export map cache is tainted by unreliable parse results ([#3062], thanks [@michaelfaith])exportMap: improve cacheKey when using flat config ([#3072], thanks [@michaelfaith])Changed
no-relative-packages]: fix typo ([#3066], thanks [@joshuaobrien])no-cycle]: dont scc for each linted file ([#3068], thanks [@soryy708])no-cycle]: adddisableSccto docs ([#3070], thanks [@soryy708])RuleTester([#3071], thanks [@G-Rath])no-restricted-paths]: fix grammar ([#3073], thanks [@unbeauvoyage])no-default-export], [no-named-export]: add test case (thanks [@G-Rath])v2.30.0Compare Source
Added
dynamic-import-chunkname]: addallowEmptyoption to allow empty leading comments ([#2942], thanks [@JiangWeixian])dynamic-import-chunkname]: Allow empty chunk name when webpackMode: 'eager' is set; add suggestions to remove name in eager mode ([#3004], thanks [@amsardesai])no-unused-modules]: AddignoreUnusedTypeExportsoption ([#3011], thanks [@silverwind])Fixed
no-extraneous-dependencies]: allow wrong path ([#3012], thanks [@chabb])no-cycle]: use scc algorithm to optimize ([#2998], thanks [@soryy708])no-duplicates]: Removing duplicates breaks in TypeScript ([#3033], thanks [@yesl-kim])newline-after-import]: fix considerComments option when require ([#2952], thanks [@developer-bandi])order]: do not compare first path segment for relative paths ([#2682]) ([#2885], thanks [@mihkeleidast])Changed
no-extraneous-dependencies]: Make glob pattern description more explicit ([#2944], thanks [@mulztob])no-unused-modules]: add console message to help debug [#2866]ExportMap: make procedures static instead of monkeypatching exportmap ([#2982], thanks [@soryy708])ExportMap: separate ExportMap instance from its builder logic ([#2985], thanks [@soryy708])order]: Add a quick note on how unbound imports and --fix ([#2640], thanks [@minervabot])exportMapBuilder: avoid hoisting ([#2989], thanks [@soryy708])ExportMap: extract "builder" logic to separate files ([#2991], thanks [@soryy708])order]: update the description of thepathGroupsExcludedImportTypesoption ([#3036], thanks [@liby])prettier/eslint-plugin-prettier (eslint-plugin-prettier)
v5.2.1Compare Source
Patch Changes
ac036ccThanks @OrlovAlexei! - build(deps): Bump synckit from 0.8.6 to 0.9.1aws/jsii (jsii-diff)
v1.104.0Compare Source
Bug Fixes
v1.103.1Compare Source
Bug Fixes
__jsii_proxy_classattributes are not preserved (#4625) (d3ec911)v1.103.0Compare Source
Features
typeguard==3.xandtypeguard==4.x(#4611) (32ae5b0)Bug Fixes
v1.102.0Compare Source
v1.101.0Compare Source
Bug Fixes
pnpm/pnpm (pnpm)
v9.12.3Compare Source
Patch Changes
node_modules, when typing "n" in the prompt that asks whether to removenode_modulesbefore installation #8655.manage-package-manager-versions=trueis set and the.toolsdirectory is corrupt.crypto.hash, when available, for improved performance #8629.package.jsonat the root of the workspace #8667.manage-package-manager-versionsis set totrue, errors spawning a self-managed version ofpnpmwill now be shown (instead of being silent).v9.12.2Compare Source
Patch Changes
v9.12.1Compare Source
Patch Changes
pnpm update --latestshould not update the automatically installed peer dependencies #6657.pnpm publishshould be able to publish from a local tarball #7950.EBUSYerrors caused by creating symlinks in paralleldlxprocesses #8604.v9.12.0Compare Source
Minor Changes
Fix peer dependency resolution dead lock #8570. This change might change some of the keys in the
snapshotsfield insidepnpm-lock.yamlbut it should happen very rarely.pnpm outdatedcommand supports now a--sort-by=nameoption for sorting outdated dependencies by package name #8523.Added the ability for
overridesto remove dependencies by specifying"-"as the field value #8572. For example, to removelodashfrom the dependencies, use this configuration inpackage.json:{ "pnpm": { "overrides": { "lodash": "-" } } }Patch Changes
pnpm list --json pkgshowed"private": falsefor a private package #8519.libcthat differ frompnpm.supportedArchitectures.libcare not downloaded #7362.ENOENTerrors caused by runningstore prunein parallel #8586.pnpm bugs#8596.v9.11.0Compare Source
Minor Changes
pnpm cachecommands for inspecting the metadata cache #8512.Patch Changes
pnpm deploywithnode-linker=hoistedproduces an emptynode_modulesdirectory #6682.pnpm deployshould work in workspace withshared-workspace-lockfile=false#8475.v9.10.0Compare Source
Minor Changes
Support for a new CLI flag,
--exclude-peers, added to thelistandwhycommands. When--exclude-peersis used, peer dependencies are not printed in the results, but dependencies of peer dependencies are still scanned #8506.Added a new setting to
package.jsonatpnpm.auditConfig.ignoreGhsasfor ignoring vulnerabilities by their GHSA code #6838.For instance:
{ "pnpm": { "auditConfig": { "ignoreGhsas": [ "GHSA-42xw-2xvc-qx8m", "GHSA-4w2v-q235-vp99", "GHSA-cph5-m8f7-6c5x", "GHSA-vh95-rmgr-6w4m" ] } } }Patch Changes
v9.9.0Compare Source
Minor Changes
Minor breaking change. This change might result in resolving your peer dependencies slightly differently but we don't expect it to introduce issues.
We had to optimize how we resolve peer dependencies in order to fix some infinite loops and out-of-memory errors during peer dependencies resolution.
When a peer dependency is a prod dependency somewhere in the dependency graph (with the same version), pnpm will resolve the peers of that peer dependency in the same way across the subgraph.
For example, we have
react-domin the peer deps of theformandbuttonpackages.cardhasreact-domandreactas regular dependencies andcardis a dependency ofform.These are the direct dependencies of our example project:
These are the dependencies of card:
When resolving peers, pnpm will not re-resolve
react-domforcard, even thoughcardshadowsreact@16from the root withreact@17. So, all 3 packages (form,card, andbutton) will usereact-dom@16, which in turn usesreact@16.formwill usereact@16, whilecardandbuttonwill usereact@17.Before this optimization
react-dom@16was duplicated for thecard, so thatcardandbuttonwould use areact-dom@16instance that usesreact@17.Before the change:
After the change
Patch Changes
pnpm deployshould write thenode_modules/.modules.yamlto thenode_modulesdirectory within the deploy directory #7731.node_modulesif it already points to the right location pnpm/symlink-dir#54.v9.8.0Compare Source
Minor Changes
Added a new command for upgrading pnpm itself when it isn't managed by Corepack:
pnpm self-update. This command will work, when pnpm was installed via the standalone script from the pnpm installation page #8424.When executed in a project that has a
packageManagerfield in itspackage.jsonfile, pnpm will update its version in thepackageManagerfield.Patch Changes
CLI tools installed in the root of the workspace should be added to the PATH, when running scripts and
use-node-versionis set.pnpm setupshould never switch to another version of pnpm.This fixes installation with the standalone script from a directory that has a
package.jsonwith thepackageManagerfield. pnpm was installing the version of pnpm specified in thepackageManagerfield due to this issue.Ignore non-string value in the os, cpu, libc fields, which checking optional dependencies #8431.
Remember the state of edit dir, allow running
pnpm patch-committhe second time without having to re-runpnpm patch.v9.7.1Compare Source
Patch Changes
public-hoist-patternandhoist-patternvia env variables #8339.pnpm setupno longer creates Batch/Powershell scripts on Linux and macOS #8418.pnpm execnow supports executionEnv #8356.pnpmfield, add warnings for non-rootpnpmsubfields that aren'texecutionEnv#8143.patch-commitin which relative path is rejected #8405.@pnpm/exeto v20.v9.7.0Compare Source
Minor Changes
Added pnpm version management to pnpm. If the
manage-package-manager-versionssetting is set totrue, pnpm will switch to the version specified in thepackageManagerfield ofpackage.json#8363. This is the same field used by Corepack. Example:{ "packageManager": "[email protected]" }Added the ability to apply patch to all versions:
If the key of
pnpm.patchedDependenciesis a package name without a version (e.g.pkg), pnpm will attempt to apply the patch to all versions ofthe package. Failures will be skipped.
If it is a package name and an exact version (e.g.
[email protected]), pnpm will attempt to apply the patch to that exact version only. Failures willcause pnpm to fail.
If there's only one version of
pkginstalled,pnpm patch pkgand subsequentpnpm patch-commit $edit_dirwill create an entry namedpkginpnpm.patchedDependencies. And pnpm will attempt to apply this patch to other versions ofpkgin the future.If there are multiple versions of
pkginstalled,pnpm patch pkgwill ask which version to edit and whether to attempt to apply the patch to all.If the user chooses to apply the patch to all,
pnpm patch-commit $edit_dirwould create apkgentry inpnpm.patchedDependencies.If the user chooses not to apply the patch to all,
pnpm patch-commit $edit_dirwould create a[email protected]entry inpnpm.patchedDependencieswithx.y.zbeing the version the user chose to edit.If the user runs
pnpm patch [email protected]withx.y.zbeing the exact version ofpkgthat has been installed,pnpm patch-commit $edit_dirwill alwayscreate a
[email protected]entry inpnpm.patchedDependencies.Change the default edit dir location when running
pnpm patchfrom a temporary directory tonode_modules/.pnpm_patches/pkg[@​version]to allow the code editor to open the edit dir in the same file tree as the main project.Substitute environment variables in config keys #6679.
Patch Changes
pnpm installshould runnode-gyp rebuildif the project has abinding.gypfile even if the project doesn't have an install script #8293.v9.6.0Compare Source
Minor Changes
pnpm.executionEnv.nodeVersioninpackage.json) for running lifecycle scripts per each package in a workspace #6720.catalogs:protocol #8303.Patch Changes
pnpm deploycommand now supports thecatalog:protocol #8298.pnpm outdatedcommand now supports thecatalog:protocol #8304.pnpm patchwithoutnode_modules/.modules.yaml#8257.pnpm execcommand #7608.v9.5.0Compare Source
Minor Changes
Added support for catalogs 8122.
Catalogs may be declared in the
pnpm-workspace.yamlfile. For example:v9.4.0Compare Source
Minor Changes
strict-store-pkg-content-checksetting tofalse#4724.Patch Changes
package-manager-strict-versionmissing in config #8195.v9.3.0Compare Source
Minor Changes
peers-suffix-max-lengthsetting #8177.Patch Changes
reporter-hide-prefixtotrueby default forpnpm exec. In order to show prefix, the user now has to explicitly setreporter-hide-prefix=false#8174.v9.2.0Compare Source
Minor Changes
package-manager-strict-versionis set totrue, pnpm will fail if its version doesn't exactly match the version in the "packageManager" field ofpackage.json.Patch Changes
@yarnpkg/pnpto the latest version, fixing issue withnode:imports #8161.package.json#8087.execnow also streams prefixed output when--recursiveor--parallelis specified just asrundoes #8065.v9.1.4Compare Source
Patch Changes
v9.1.3Compare Source
Patch Changes
optional=false#8066.prettier/prettier (prettier)
v3.3.3Compare Source
diff
Add parentheses for nullish coalescing in ternary (#16391 by @cdignam-segment)
This change adds clarity to operator precedence.
Add parentheses for decorator expressions (#16458 by @y-schneider)
Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.
Support
@letdeclaration syntax (#16474 by @sosukesuzuki)Adds support for Angular v18
@letdeclaration syntax.Please see the following code example. The
@letdeclaration allows you to define local variables within the template:For more details, please refer to the excellent blog post by the Angular Team: Introducing @let in Angular.
We also appreciate the Angular Team for kindly answering our questions to implement this feature.
npm/node-semver (semver)
v7.6.3Compare Source
Bug Fixes
73a3d79#726 optimize Range parsing and formatting (#726) (@jviide)Documentation
2975ece#719 fix extra backtick typo (#719) (@stdavis)kulshekhar/ts-jest (ts-jest)
v29.2.5Compare Source
v29.2.4Compare Source
v29.2.3Compare Source
v29.2.2Compare Source
v29.2.1Compare Source
v29.2.0Compare Source
Bug Fixes
Features
presetstotransformconfig (22fb027)Code refactoring
TsJestTransformerOptionstype everywhere possibly (7d001be)react-appto use Vite (827c8ad)microsoft/TypeScript (typescript)
v5.6.3: TypeScript 5.6.3Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
Downloads are available on:
v5.6.2: TypeScript 5.6Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
Downloads are available on:
v5.5.4: TypeScript 5.5.4Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
Downloads are available on:
v5.5.3: TypeScript 5.5.3Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the
Downloads are available on:
Configuration
📅 Schedule: Branch creation - "before 2am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Renovate Bot.