Skip to content
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 #217

Merged
merged 1 commit into from
Jun 6, 2023
Merged

chore(deps): update all non-major dependencies #217

merged 1 commit into from
Jun 6, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 13, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@typescript-eslint/eslint-plugin ^5.59.5 -> ^5.59.9 age adoption passing confidence
@typescript-eslint/parser ^5.59.5 -> ^5.59.9 age adoption passing confidence
c8 ^7.13.0 -> ^7.14.0 age adoption passing confidence
esbuild 0.17.18 -> 0.17.19 age adoption passing confidence
eslint (source) ^8.40.0 -> ^8.42.0 age adoption passing confidence
expect-type ^0.15.0 -> ^0.16.0 age adoption passing confidence
pnpm (source) 8.5.0 -> 8.6.1 age adoption passing confidence
postcss (source) ^8.4.23 -> ^8.4.24 age adoption passing confidence
release-it ^15.10.3 -> ^15.11.0 age adoption passing confidence
typescript (source) ^5.0.4 -> ^5.1.3 age adoption passing confidence
vite (source) ^4.3.5 -> ^4.3.9 age adoption passing confidence
vitest ^0.31.0 -> ^0.31.4 age adoption passing confidence

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.59.9

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.59.8

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.59.7

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.59.6

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.59.9

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.59.8

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.59.7

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.59.6

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

bcoe/c8

v7.14.0

Compare Source

Features
  • added a new CLI arg --merge-async to asynchronously and incrementally merge process coverage files to avoid OOM due to heap exhaustion (#​469) (45f2f84)
evanw/esbuild

v0.17.19

Compare Source

  • Fix CSS transform bugs with nested selectors that start with a combinator (#​3096)

    This release fixes several bugs regarding transforming nested CSS into non-nested CSS for older browsers. The bugs were due to lack of test coverage for nested selectors with more than one compound selector where they all start with the same combinator. Here's what some problematic cases look like before and after these fixes:

    /* Original code */
.foo {
  > &a,
  > &b {
    color: red;
  }
}
.bar {
  > &a,
  + &b {
    color: green;
  }
}

/* Old output (with --target=chrome90) */
.foo :is(> .fooa, > .foob) {
  color: red;
}
.bar :is(> .bara, + .barb) {
  color: green;
}

/* New output (with --target=chrome90) */
.foo > :is(a.foo, b.foo) {
  color: red;
}
.bar > a.bar,
.bar + b.bar {
  color: green;
}

  • Fix bug with TypeScript parsing of instantiation expressions followed by = (#​3111)

    This release fixes esbuild's TypeScript-to-JavaScript conversion code in the case where a potential instantiation expression is followed immediately by a = token (such that the trailing > becomes a >= token). Previously esbuild considered that to still be an instantiation expression, but the official TypeScript compiler considered it to be a >= operator instead. This release changes esbuild's interpretation to match TypeScript. This edge case currently appears to be problematic for other TypeScript-to-JavaScript converters as well:

    Original code TypeScript esbuild 0.17.18 esbuild 0.17.19 Sucrase Babel
    x<y>=a<b<c>>() x<y>=a(); x=a(); x<y>=a(); x=a() Invalid left-hand side in assignment expression

  • Avoid removing unrecognized directives from the directive prologue when minifying (#​3115)

    The directive prologue in JavaScript is a sequence of top-level string expressions that come before your code. The only directives that JavaScript engines currently recognize are use strict and sometimes use asm. However, the people behind React have made up their own directive for their own custom dialect of JavaScript. Previously esbuild only preserved the use strict directive when minifying, although you could still write React JavaScript with esbuild using something like --banner:js="'your directive here';". With this release, you can now put arbitrary directives in the entry point and esbuild will preserve them in its minified output:

    // Original code
'use wtf'; console.log(123)

// Old output (with --minify)
console.log(123);

// New output (with --minify)
"use wtf";console.log(123);

    Note that this means esbuild will no longer remove certain stray top-level strings when minifying. This behavior is an intentional change because these stray top-level strings are actually part of the directive prologue, and could potentially have semantics assigned to them (as was the case with React).

  • Improved minification of binary shift operators

    With this release, esbuild's minifier will now evaluate the << and >>> operators if the resulting code would be shorter:

    // Original code
console.log(10 << 10, 10 << 20, -123 >>> 5, -123 >>> 10);

// Old output (with --minify)
console.log(10<<10,10<<20,-123>>>5,-123>>>10);

// New output (with --minify)
console.log(10240,10<<20,-123>>>5,4194303);
eslint/eslint

v8.42.0

Compare Source

Features

  • b8448ff feat: correct no-useless-return behaviour in try statements (#​16996) (Nitin Kumar)

Bug Fixes

  • a589636 fix: Config with ignores and without files should not always apply (#​17181) (Milos Djermanovic)
  • c4fad17 fix: Correct ignore message for "node_modules" subfolders (#​17217) (Francesco Trotta)

Documentation

  • 01d7142 docs: Update README (GitHub Actions Bot)
  • e5182b7 docs: Update README (GitHub Actions Bot)

Chores

v8.41.0

Compare Source

Features

  • 880a431 feat: change default ignore pattern to **/node_modules/ in flat config (#​17184) (Milos Djermanovic)
  • 8bf5505 feat: expose shouldUseFlatConfig (#​17169) (Connor Prussin)

Bug Fixes

  • 4f5440d fix: incorrect warning message for ignored dotfiles (#​17196) (Milos Djermanovic)
  • 94da96c fix: unify LintMessage type (#​17076) (Brandon Mills)
  • 0c415cd fix: validate ignorePatterns constructor option in FlatESLint class (#​17139) (Milos Djermanovic)
  • 9682d66 fix: switch grapheme-splitter to graphemer (#​17160) (fisker Cheung)

Documentation

  • 7709b14 docs: Update README (GitHub Actions Bot)
  • 7f183e0 docs: Update triage process description (#​17157) (Nicholas C. Zakas)
  • b68346b docs: fix license to reflect relicensing of jshint (#​17165) (Stefan Bischof)

Chores

mmkal/expect-type

v0.16.0

Compare Source

What's Changed

Note that #​21 has affected behavior for intersection types, which can result in (arguably) false errors:

// @&#8203;ts-expect-error the following line doesn't compile, even though the types are arguably the same.
// See https://github.com/mmkal/expect-type/pull/21
expectTypeOf<{a: 1} & {b: 2}>().toEqualTypeOf<{a: 1; b: 2}>()

Full Changelog: mmkal/expect-type@v0.15.0...v16.0.0

pnpm/pnpm

v8.6.1

Compare Source

Patch Changes

  • When dedupe-peer-dependents is enabled (default), use the path (not id) to determine compatibility.

    When multiple dependency groups can be deduplicated, the latter ones are sorted according to number of peers to allow them to
    benefit from deduplication.

    Resolves: #​6605

  • Some minor performance improvements by removing await from loops #​6617.

Our Gold Sponsors

Our Silver Sponsors

v8.6.0

Compare Source

Minor Changes

  • Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created.

    A new field will now be present in the lockfile: settings. It will store the values of two settings: autoInstallPeers and excludeLinksFromLockfile. If someone tries to perform a frozen-lockfile installation and their active settings don't match the ones in the lockfile, then an error message will be thrown.

    The lockfile format version is bumped from v6.0 to v6.1.

    Related PR: #​6557
    Related issue: #​6312

  • A new setting, exclude-links-from-lockfile, is now supported. When enabled, specifiers of local linked dependencies won't be duplicated in the lockfile.

    This setting was primarily added for use by Bit CLI, which links core aspects to node_modules from external directories. As such, the locations may vary across different machines, resulting in the generation of lockfiles with differing locations.

Patch Changes

  • Don't print "Lockfile is up-to-date" message before finishing all the lockfile checks #​6544.
  • When updating dependencies, preserve the range prefix in aliased dependencies. So npm:foo@1.0.0 becomes npm:foo@1.1.0.
  • Print a meaningful error when a project referenced by the workspace: protocol is not found in the workspace #​4477.
  • pnpm rebuild should not fail when node-linker is set to hoisted and there are skipped optional dependencies #​6553.
  • Peers resolution should not fail when a linked in dependency resolves a peer dependency.
  • Build projects in a workspace in correct order #​6568.

Our Gold Sponsors

Our Silver Sponsors

v8.5.1

Compare Source

Patch Changes

  • Expanded missing command error, including 'did you mean' #​6492.
  • When installation fails because the lockfile is not up-to-date with the package.json file(s), print out what are the differences #​6536.
  • Normalize current working directory on Windows #​6524.

Our Gold Sponsors

Our Silver Sponsors
postcss/postcss

v8.4.24

Compare Source

  • Fixed Plugin types.
release-it/release-it

v15.11.0

Compare Source

v15.10.5

Compare Source

v15.10.4

Compare Source

Microsoft/TypeScript

v5.1.3: TypeScript 5.1.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

vitejs/vite

v4.3.9

Compare Source

v4.3.8

Compare Source

v4.3.7

Compare Source

v4.3.6

Compare Source

vitest-dev/vitest

v0.31.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.2

Compare Source

   🚀 Features
   🐞 Bug Fixes

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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@socket-security
Copy link

socket-security bot commented May 13, 2023 •
edited
Loading

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been removed or ignored.

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

@renovate renovate bot changed the title chore(deps): update devdependency esbuild to v0.17.19 chore(deps): update all non-major dependencies May 15, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 2455fde to 5061b16 Compare May 19, 2023 23:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 7c6ae17 to 18d8481 Compare May 29, 2023 18:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from c698d64 to b8925fa Compare June 5, 2023 18:32
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b8925fa to 34c8cc6 Compare June 6, 2023 16:59
@socket-security
Copy link

New and updated dependency changes detected. Learn more about Socket for GitHub ↗︎

Packages Version New capabilities Transitives1 Size Publisher
esbuild ⬆️ 0.17.18...0.17.19 None +0/-0 130 kB evanw
c8 ⬆️ 7.13.0...7.14.0 filesystem +0/-0 38.7 kB oss-bot
vite ⬆️ 4.3.5...4.3.9 None +2/-2 3.58 MB vitebot
vitest ⬆️ 0.31.0...0.31.4 None +11/-11 5.47 MB oreanno
release-it ⬆️ 15.10.3...15.11.0 None +33/-40 12.5 MB webpro
eslint ⬆️ 8.40.0...8.42.0 None +2/-5 3.71 MB eslintbot
postcss ⬆️ 8.4.23...8.4.24 None +0/-0 194 kB ai
expect-type ⬆️ 0.15.0...0.16.0 None +0/-0 39.9 kB mmkale

🚮 Removed packages: @typescript-eslint/eslint-plugin@5.59.5, @typescript-eslint/parser@5.59.5, typescript@5.0.4

Footnotes

  1. https://docs.socket.dev ↩

@danielroe danielroe merged commit f8526d8 into main Jun 6, 2023
@danielroe danielroe deleted the renovate/all-minor-patch branch June 6, 2023 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@danielroe