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.

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

chore(deps): update non-major #175

Merged
merged 1 commit into from
Jun 19, 2024
Merged

chore(deps): update non-major #175

merged 1 commit into from
Jun 19, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 19, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@sanity/pkg-utils ^6.9.1 -> ^6.10.0 age adoption passing confidence devDependencies minor
@sanity/ui (source) ^2.3.1 -> ^2.4.0 age adoption passing confidence devDependencies minor
@typescript-eslint/eslint-plugin (source) ^7.12.0 -> ^7.13.1 age adoption passing confidence devDependencies minor
@typescript-eslint/parser (source) ^7.12.0 -> ^7.13.1 age adoption passing confidence devDependencies minor
@vitejs/plugin-react (source) ^4.3.0 -> ^4.3.1 age adoption passing confidence devDependencies patch
esbuild ^0.21.4 -> ^0.21.5 age adoption passing confidence devDependencies patch
eslint-plugin-react ^7.34.2 -> ^7.34.3 age adoption passing confidence devDependencies patch
peter-evans/create-pull-request 6d6857d -> c5a7806 action digest
prettier (source) ^3.3.1 -> ^3.3.2 age adoption passing confidence devDependencies patch
vite (source) ^5.2.13 -> ^5.3.1 age adoption passing confidence devDependencies minor

Release Notes

sanity-io/pkg-utils (@​sanity/pkg-utils)

v6.10.0

Compare Source

Features

v6.9.3

Compare Source

Bug Fixes

v6.9.2

Compare Source

Bug Fixes
sanity-io/ui (@​sanity/ui)

v2.4.0

Compare Source

Features

v2.3.6

Compare Source

Bug Fixes

v2.3.5

Compare Source

Bug Fixes

v2.3.4

Compare Source

Bug Fixes
  • menu: allow overriding selected property on MenuButton (eae34c1)

v2.3.3

Compare Source

Bug Fixes
  • theme: placeholder color in dark mode (94c5887)

v2.3.2

Compare Source

Bug Fixes
  • button: use JSX instead of createElement (d1f5648)
  • menu-button: handle child refs safely (9ca1312)
  • menu-group: use JSX instead of createElement (061f67d)
  • menu-item: use JSX instead of createElement (c61aa10)
  • text-input: use JSX instead of createElement (45c1fcf)
  • tooltip: handle child refs safely (92b12a7)
  • tree-item: use JSX instead of createElement (c4d66c5)
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v7.13.1

Compare Source

🩹 Fixes
  • eslint-plugin: [prefer-readonly] refine report locations

  • eslint-plugin: [return-await] support explicit resource management

  • eslint-plugin: [no-unsafe-member-access] differentiate a types-error any from a true any

❤️ Thank You
  • Kirk Waiblinger
  • Yukihiro Hasegawa

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

v7.13.0

Compare Source

🚀 Features
  • typescript-estree: require import = require() argument to be a string literal

  • typescript-estree: forbid .body, .async, .generator on declare function

  • eslint-plugin: [no-dynamic-delete] allow all string literals as index

🩹 Fixes
  • ast-spec: function-call-like callee should be Expression not LeftHandSideExpression

  • scope-manager: handle index signature in class

  • eslint-plugin: [init-declarations] refine report locations

  • eslint-plugin: [no-base-to-string] make error message more nuanced

  • eslint-plugin: [no-unsafe-assignment] be more specific about error types

  • eslint-plugin: [no-magic-numbers] fix implementation of the ignore option

❤️ Thank You
  • Fotis Papadogeorgopoulos
  • Joshua Chen
  • Kirk Waiblinger
  • Tobiloba Adedeji
  • Vinccool96
  • YeonJuan

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

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

v7.13.1

Compare Source

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

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

v7.13.0

Compare Source

🚀 Features
  • parser, typescript-estree: export withoutProjectParserOptions utility
❤️ Thank You
  • Fotis Papadogeorgopoulos
  • Joshua Chen
  • Kirk Waiblinger
  • Tobiloba Adedeji
  • Vinccool96
  • YeonJuan

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

vitejs/vite-plugin-react (@​vitejs/plugin-react)

v4.3.1

Compare Source

Fix support for React Compiler with React 18

The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom runtimeModule: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43

When using a custom runtimeModule, the plugin will not try to pre-optimize react/compiler-runtime dependency.

Reminder: Vite expect code outside of node_modules to be ESM, so you will need to update the gist with import React from 'react'.

evanw/esbuild (esbuild)

v0.21.5

Compare Source

  • Fix Symbol.metadata on classes without a class decorator (#​3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#​3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
    import tasty from "./bagel.js" with { type: "bagel" }

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
    import tasty from "./tasty.bagel" with { type: "bagel" }
  • Support import attributes with glob-style imports (#​3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
      const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
      return unpackLocale(locale, data)
    }

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data
    
        example.ts:2:28:
          2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
            ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~
    

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#​3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

    {
      "compilerOptions": {
        "paths": {
          "js/*": ["${configDir}/dist/js/*"]
        }
      }
    }

    You can read more in TypeScript's blog post about their upcoming 5.5 release. Note that this feature does not make use of template literals (you need to use "${configDir}/dist/js/*" not `${configDir}/dist/js/*`). The syntax for tsconfig.json is still just JSON with comments, and JSON syntax does not allow template literals. This feature only recognizes ${configDir} in strings for certain path-like properties, and only at the beginning of the string.

  • Fix internal error with --supported:object-accessors=false (#​3794)

    This release fixes a regression in 0.21.0 where some code that was added to esbuild's internal runtime library of helper functions for JavaScript decorators fails to parse when you configure esbuild with --supported:object-accessors=false. The reason is that esbuild introduced code that does { get [name]() {} } which uses both the object-extensions feature for the [name] and the object-accessors feature for the get, but esbuild was incorrectly only checking for object-extensions and not for object-accessors. Additional tests have been added to avoid this type of issue in the future. A workaround for this issue in earlier releases is to also add --supported:object-extensions=false.

jsx-eslint/eslint-plugin-react (eslint-plugin-react)

v7.34.3

Compare Source

Fixed
  • [prop-types]: null-check rootNode before calling getScope (#​3762 @​crnhrv)
  • [boolean-prop-naming]: avoid a crash with a spread prop (#​3733 @​ljharb)
  • [jsx-boolean-value]: assumeUndefinedIsFalse with never must not allow explicit true value (#​3757 @​6uliver)
  • [no-object-type-as-default-prop]: enable rule for components with many parameters (#​3768 @​JulienR1)
  • [jsx-key]: incorrect behavior for checkKeyMustBeforeSpread with map callbacks (#​3769 @​akulsr0)
prettier/prettier (prettier)

v3.3.2

Compare Source

diff

Fix handlebars path expressions starts with @ (#​16358 by @​Princeyadav05)
{{! Input }}
<div>{{@&#8203;x.y.z}}</div>

{{! Prettier 3.3.1 }}
<div>{{@&#8203;x}}</div>

{{! Prettier 3.3.2 }}
<div>{{@&#8203;x.y.z}}</div>
vitejs/vite (vite)

v5.3.1

Compare Source

v5.3.0

Compare Source


Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (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.


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

This PR has been generated by Mend Renovate using a curated preset maintained by Sanity. View repository job log here

Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/[email protected] environment, filesystem, network, shell 0 133 kB evanw
npm/[email protected] environment, filesystem, unsafe 0 8.25 MB prettier-bot

🚮 Removed packages: npm/[email protected], npm/[email protected]

View full report↗︎

@stipsan stipsan enabled auto-merge June 19, 2024 11:21
@stipsan stipsan added this pull request to the merge queue Jun 19, 2024
Merged via the queue into main with commit da31b0c Jun 19, 2024
7 checks passed
@stipsan stipsan deleted the renovate/non-major branch June 19, 2024 11:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant