Skip to content

fix(deps): update all non-major dependencies #159

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
Merged
merged 1 commit into from
Dec 31, 2024
Merged

fix(deps): update all non-major dependencies #159

merged 1 commit into from
Dec 31, 2024

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 31, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@swc/core (source) ^1.10.0 -> ^1.10.4 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) ^8.17.0 -> ^8.19.0 age adoption passing confidence
chalk ^5.3.0 -> ^5.4.1 age adoption passing confidence
esbuild ^0.24.0 -> ^0.24.2 age adoption passing confidence
eslint (source) ^9.16.0 -> ^9.17.0 age adoption passing confidence
eslint-plugin-import-x ^4.5.0 -> ^4.6.1 age adoption passing confidence
jiti ^2.4.1 -> ^2.4.2 age adoption passing confidence
pnpm (source) 9.14.4 -> 9.15.2 age adoption passing confidence
release-it ^17.10.0 -> ^17.11.0 age adoption passing confidence
typescript-eslint (source) ^8.17.0 -> ^8.19.0 age adoption passing confidence

Release Notes

swc-project/swc (@​swc/core)

v1.10.4

Compare Source

Bug Fixes

v1.10.3

Compare Source

Bug Fixes
  • (es/codegen) Emit semicolon after using declarations (#​9816) (556d924)

v1.10.2

Compare Source

Bug Fixes
Documentation

v1.10.1

Compare Source

Bug Fixes
  • (es/resolver) Fix wrong syntax context of vars with the same names as catch params (#​9786) (5a44c6b)
Features
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v8.19.0

Compare Source

🚀 Features
  • eslint-plugin: [strict-boolean-expressions] check array predicate functions' return statements (#​10106)
🩹 Fixes
  • eslint-plugin: [member-ordering] ignore method overloading (#​10536)
  • eslint-plugin: [consistent-indexed-object-style] don't report on indirect circular references (#​10537)
  • eslint-plugin: [array-type] autofix with conditional types needs parentheses (#​10522)
  • eslint-plugin: add getConstraintInfo to handle generic constraints better (#​10496)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.18.2

Compare Source

🩹 Fixes
  • eslint-plugin: [no-unnecessary-condition] handle noUncheckedIndexedAccess true (#​10514)
  • eslint-plugin: [consistent-type-assertions] allow default assertionStyle option (#​10512)
  • eslint-plugin: [no-unnecessary-type-arguments] handle type/value context (#​10503)
  • eslint-plugin: [no-unsafe-type-assertion] fix for unsafe assertion to a constrained type parameter (#​10461)
  • eslint-plugin: [consistent-indexed-object-style] use a suggestion over an auto-fix if can't reliably determine that produced index signature is valid (#​10490)
  • eslint-plugin: [no-unnecessary-condition] don't flag values of an unconstrained or valid type parameter (#​10473)
  • eslint-plugin: [prefer-reduce-type-parameter] don't report cases in which the fix results in a type error (#​10494)
  • eslint-plugin: [no-deprecated] not reporting usages of deprecated declared constants as object value (#​10498)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.18.1

Compare Source

🩹 Fixes
  • scope-manager: visit params decorator before nest scope (#​10475)
  • eslint-plugin: [no-unnecessary-condition] better message when comparing between literal types (#​10454)
  • eslint-plugin: use consistent naming for asserting types and casting values (#​10472)
  • eslint-plugin: [no-unnecessary-boolean-literal-compare] flag values of a type parameter with boolean type constraints (#​10474)
  • eslint-plugin: handle string like index type (#​10460)
  • eslint-plugin: [no-unnecessary-template-expression] don't report when an expression includes comment (#​10444)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.18.0

Compare Source

🚀 Features
  • eslint-plugin: [switch-exhaustiveness-check] add support for "no default" comment (#​10218)
  • eslint-plugin: [no-deprecated] report on super call of deprecated constructor (#​10397)
🩹 Fixes
  • eslint-plugin: [use-unknown-in-catch-callback-variable] only flag function literals (#​10436)
  • eslint-plugin: [no-base-to-string] handle more robustly when multiple toString() declarations are present for a type (#​10432)
  • eslint-plugin: [no-deprecated] check if a JSX attribute is deprecated (#​10374)
  • typescript peer dependency (#​10373)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

chalk/chalk (chalk)

v5.4.1

Compare Source

v5.4.0

Compare Source

  • Update CIRCLECI environments to return level 3 color support f838120
evanw/esbuild (esbuild)

v0.24.2

Compare Source

  • Fix regression with --define and import.meta (#​4010, #​4012, #​4013)

    The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

    This fix was contributed by @​sapphi-red.

v0.24.1

Compare Source

  • Allow es2024 as a target in tsconfig.json (#​4004)

    TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

    { "compilerOptions": { "target": "ES2024" } }

    As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

    This fix was contributed by @​billyjanitsch.

  • Allow automatic semicolon insertion after get/set

    This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

    class Foo { get *x() {} set *y() {} }

    The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

  • Allow quoted property names in --define and --pure (#​4008)

    The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

    // The following code now transforms to "return true;\n" console.log(esbuild.transformSync( `return process.env['SOME-TEST-VAR']`, { define: { 'process.env["SOME-TEST-VAR"]': 'true' } }, ))

    Note that if you're passing values like this on the command line using esbuild's --define flag, then you'll need to know how to escape quote characters for your shell. You may find esbuild's JavaScript API more ergonomic and portable than writing shell code.

  • Minify empty try/catch/finally blocks (#​4003)

    With this release, esbuild will now attempt to minify empty try blocks:

    // Original code try {} catch { foo() } finally { bar() } // Old output (with --minify) try{}catch{foo()}finally{bar()} // New output (with --minify) bar();

    This can sometimes expose additional minification opportunities.

  • Include entryPoint metadata for the copy loader (#​3985)

    Almost all entry points already include a entryPoint field in the outputs map in esbuild's build metadata. However, this wasn't the case for the copy loader as that loader is a special-case that doesn't behave like other loaders. This release adds the entryPoint field in this case.

  • Source mappings may now contain null entries (#​3310, #​3878)

    With this change, sources that result in an empty source map may now emit a null source mapping (i.e. one with a generated position but without a source index or original position). This change improves source map accuracy by fixing a problem where minified code from a source without any source mappings could potentially still be associated with a mapping from another source file earlier in the generated output on the same minified line. It manifests as nonsensical files in source mapped stack traces. Now the null mapping "resets" the source map so that any lookups into the minified code without any mappings resolves to null (which appears as the output file in stack traces) instead of the incorrect source file.

    This change shouldn't affect anything in most situations. I'm only mentioning it in the release notes in case it introduces a bug with source mapping. It's part of a work-in-progress future feature that will let you omit certain unimportant files from the generated source map to reduce source map size.

  • Avoid using the parent directory name for determinism (#​3998)

    To make generated code more readable, esbuild includes the name of the source file when generating certain variable names within the file. Specifically bundling a CommonJS file generates a variable to store the lazily-evaluated module initializer. However, if a file is named index.js (or with a different extension), esbuild will use the name of the parent directory instead for a better name (since many packages have files all named index.js but have unique directory names).

    This is problematic when the bundle entry point is named index.js and the parent directory name is non-deterministic (e.g. a temporary directory created by a build script). To avoid non-determinism in esbuild's output, esbuild will now use index instead of the parent directory in this case. Specifically this will happen if the parent directory is equal to esbuild's outbase API option, which defaults to the lowest common ancestor of all user-specified entry point paths.

  • Experimental support for esbuild on NetBSD (#​3974)

    With this release, esbuild now has a published binary executable for NetBSD in the @esbuild/netbsd-arm64 npm package, and esbuild's installer has been modified to attempt to use it when on NetBSD. Hopefully this makes installing esbuild via npm work on NetBSD. This change was contributed by @​bsiegert.

    ⚠️ Note: NetBSD is not one of Node's supported platforms, so installing esbuild may or may not work on NetBSD depending on how Node has been patched. This is not a problem with esbuild. ⚠️

eslint/eslint (eslint)

v9.17.0

Compare Source

un-ts/eslint-plugin-import-x (eslint-plugin-import-x)

v4.6.1

Compare Source

Patch Changes

v4.6.0

Compare Source

Minor Changes

  • #​209 46d2360 Thanks @​SukkaW! - When eslint-plugin-import-x was forked from eslint-plugin-import, we copied over the default resolver (which is eslint-import-resolver-node) as well. However, this resolver doesn't supports exports in the package.json file, and the current maintainer of the eslint-import-resolver-node (ljharb) doesn't have the time implementing this feature and he locked the issue https://github.com/import-js/eslint-plugin-import/issues/1810.

    So we decided to implement our own resolver that "just works". The new resolver is built upon the enhanced-resolve that implements the full Node.js Resolver Algorithm. The new resolver only implements the import resolver interface v3, which means you can only use it with ESLint Flat config. For more details about the import resolver interface v3, please check out #​192.

    In the next major version of eslint-plugin-import-x, we will remove the eslint-import-resolver-node and use this new resolver by default. In the meantime, you can try out this new resolver by setting the import-x/resolver-next option in your eslint.config.js file:

    // eslint.config.js const eslintPluginImportX = require('eslint-plugin-import-x'); const { createNodeResolver } = eslintPluginImportX; module.exports = { plugins: { 'import-x': eslintPluginImportX, }, settings: { 'import-x/resolver-next': [ // This is the new resolver we are introducing createNodeResolver({ /**  * The allowed extensions the resolver will attempt to find when resolving a module  * By default it uses a relaxed extension list to search for both ESM and CJS modules  * You can customize this list to fit your needs  *  * @​default ['.mjs', '.cjs', '.js', '.json', '.node']  */ extensions?: string[]; /**  * Optional, the import conditions the resolver will used when reading the exports map from "package.json"  * By default it uses a relaxed condition list to search for both ESM and CJS modules  * You can customize this list to fit your needs  *  * @​default ['default', 'module', 'import', 'require']  */ conditions: ['default', 'module', 'import', 'require'], // You can pass more options here, see the enhanced-resolve documentation for more details // https://github.com/webpack/enhanced-resolve/tree/v5.17.1?tab=readme-ov-file#resolver-options }), // you can add more resolvers down below require('eslint-import-resolver-typescript').createTypeScriptImportResolver( /** options of eslint-import-resolver-typescript */ ) ], }, };

    We do not plan to implement reading baseUrl and paths from the tsconfig.json file in this resolver. If you need this feature, please checkout eslint-import-resolver-typescript (also powered by enhanced-resolve), eslint-import-resolver-oxc (powered by oxc-resolver), eslint-import-resolver-next (also powered by oxc-resolver), or other similar resolvers.

Patch Changes

v4.5.1

Compare Source

Patch Changes
unjs/jiti (jiti)

v2.4.2

Compare Source

compare changes

🩹 Fixes
  • cache: Add +map suffix to fs entries when sourceMaps enabled (#​352)
  • Use native require cache of loaded entries only (#​348)
🏡 Chore
✅ Tests
  • Simplify snapshot tests (#​351)
❤️ Contributors
pnpm/pnpm (pnpm)

v9.15.2: pnpm 9.15.2

Compare Source

Patch Changes

  • Fixed publish/pack error with workspace dependencies with relative paths #​8904. It was broken in v9.4.0 (398472c).
  • Use double quotes in the command suggestion by pnpm patch on Windows #​7546.
  • Do not fall back to SSH, when resolving a git-hosted package if git ls-remote works via HTTPS #​8906.
  • Improve how packages with blocked lifecycle scripts are reported during installation. Always print the list of ignored scripts at the end of the output. Include a hint about how to allow the execution of those packages.

Platinum Sponsors

Bit Bit Figma

Gold Sponsors

Discord Prisma
u|screen JetBrains
Nx CodeRabbit
Route4Me Workleap
Canva

v9.15.1

Compare Source

v9.15.0

Compare Source

release-it/release-it (release-it)

v17.11.0

Compare Source

  • Update dependencies (182e992)
  • GitLab Generic Package Repository for assets (#​1189) (54399c9)
  • fix(gitlab): don't set Content-Type header when uploading release assets (#​1183) (04a36d2)
  • Fixed GitBase.getLatestVersion to computed formatted tagTemplate before using it for latestTag computation (#​1170) (09d7d1b)
  • Add git-cliff example (#​1176) (b161114)
  • Move configuration options to existing doc pages + table format, shorten (28213bf)
  • Add docs for configuration options (#​1155) (667cd6a)
  • Improve docs on Tag Match (#​1165) (716b44f)
typescript-eslint/typescript-eslint (typescript-eslint)

v8.19.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.18.2

Compare Source

🩹 Fixes
  • typescript-eslint: export types so that declarations can be named for dts files (#​10513)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.18.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.18.0

Compare Source

🩹 Fixes
❤️ Thank You
  • rtritto

You can read about our versioning strategy and releases on our website.

Configuration

📅 Schedule: Branch creation - "* 0-3 1 * *" in timezone Pacific/Auckland, 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.

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

This PR was generated by Mend Renovate. View the repository job log.
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Dec 31, 2024
@coderabbitai
Copy link

coderabbitai bot commented Dec 31, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.
@codecov-commenter
Copy link

codecov-commenter commented Dec 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (ac33e5b) to head (446a6b1).

Additional details and impacted files 
@@ Coverage Diff @@ ## main #159 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 3 3 Lines 31 31 Branches 4 4 ========================================= Hits 31 31

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.
@renovate renovate bot merged commit 0f91cc7 into main Dec 31, 2024
5 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch December 31, 2024 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

2 participants

@codecov-commenter