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

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

Merged
merged 2 commits into from
Feb 15, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 27, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@floating-ui/dom (source) 1.5.4 -> 1.6.3 age adoption passing confidence
@storybook/addon-actions (source) 7.6.10 -> 7.6.15 age adoption passing confidence
@storybook/addon-essentials (source) 7.6.10 -> 7.6.15 age adoption passing confidence
@storybook/addon-interactions (source) 7.6.10 -> 7.6.15 age adoption passing confidence
@storybook/addon-links (source) 7.6.10 -> 7.6.15 age adoption passing confidence
@storybook/blocks (source) 7.6.10 -> 7.6.15 age adoption passing confidence
@storybook/builder-vite (source) 7.6.10 -> 7.6.15 age adoption passing confidence
@storybook/cli (source) 7.6.10 -> 7.6.15 age adoption passing confidence
@storybook/test (source) 7.6.10 -> 7.6.15 age adoption passing confidence
@storybook/vue3 (source) 7.6.10 -> 7.6.15 age adoption passing confidence
@storybook/vue3-vite (source) 7.6.10 -> 7.6.15 age adoption passing confidence
@vitejs/plugin-vue (source) 5.0.3 -> 5.0.4 age adoption passing confidence
@vue/compiler-sfc (source) 3.4.14 -> 3.4.19 age adoption passing confidence
@vue/test-utils 2.4.3 -> 2.4.4 age adoption passing confidence
esbuild ^0.19.11 -> ^0.20.0 age adoption passing confidence
happy-dom 13.1.4 -> 13.3.8 age adoption passing confidence
playwright (source) 1.41.1 -> 1.41.2 age adoption passing confidence
scroll-doctor 2.0.0 -> 2.0.2 age adoption passing confidence
shikiji (source) ^0.9.0 -> ^0.10.0 age adoption passing confidence
storybook (source) 7.6.10 -> 7.6.15 age adoption passing confidence
vite (source) 5.0.12 -> 5.1.2 age adoption passing confidence
vitest (source) 1.2.1 -> 1.2.2 age adoption passing confidence
vue (source) 3.4.14 -> 3.4.19 age adoption passing confidence

Release Notes

floating-ui/floating-ui (@​floating-ui/dom)

v1.6.3

Compare Source

Patch Changes
  • fix: calculate reference element offset relative to offsetParent iframe. Fixes issue with positioning in nested iframes, such as the following:
<html>
  <iframe>
    <div>floating</div>
    <iframe>
      <div>reference</div>
    </iframe>
  </iframe>
</html>

v1.6.2

Compare Source

Patch Changes
  • fix: top layer element positioning and collision detection when using absolute strategy

v1.6.1

Compare Source

Patch Changes
  • perf: avoid getContainingBlock call for non-top layer elements

v1.6.0

Compare Source

Minor Changes
Patch Changes
  • Update dependencies: @floating-ui/core@1.6.0
storybookjs/storybook (@​storybook/addon-actions)

v7.6.15

Compare Source

v7.6.14

Compare Source

v7.6.13

Compare Source

v7.6.12

Compare Source

v7.6.11

Compare Source

storybookjs/storybook (@​storybook/addon-essentials)

v7.6.15

Compare Source

v7.6.14

Compare Source

v7.6.13

Compare Source

v7.6.12

Compare Source

v7.6.11

Compare Source

storybookjs/storybook (@​storybook/addon-interactions)

v7.6.15

Compare Source

v7.6.14

Compare Source

v7.6.13

Compare Source

7.6.13

v7.6.12

Compare Source

v7.6.11

Compare Source

storybookjs/storybook (@​storybook/addon-links)

v7.6.15

Compare Source

v7.6.14

Compare Source

v7.6.13

Compare Source

7.6.13

v7.6.12

Compare Source

v7.6.11

Compare Source

storybookjs/storybook (@​storybook/blocks)

v7.6.15

Compare Source

  • Interaction: Make sure that adding spies doesn't cause infinite loops with self referencing args #​26019, thanks @​kasperpeulen!

v7.6.14

Compare Source

v7.6.13

Compare Source

v7.6.12

Compare Source

v7.6.11

Compare Source

storybookjs/storybook (@​storybook/cli)

v7.6.15

Compare Source

v7.6.14

Compare Source

v7.6.13

Compare Source

v7.6.12

Compare Source

v7.6.11

Compare Source

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

v5.0.4

vuejs/core (@​vue/compiler-sfc)

v3.4.19

Compare Source

Bug Fixes
Features

Note: this warning is categorized as a feature but released in a patch because it does not affect public APIs.

Performance Improvements

v3.4.18

Compare Source

Bug Fixes

v3.4.17

Compare Source

Reverts

v3.4.16

Compare Source

Bug Fixes
Reverts

v3.4.15

Compare Source

Bug Fixes
  • compiler-sfc: fix type resolution for symlinked node_modules structure w/ pnpm (75e866b), closes #​10121
  • correct url for production error reference links (c3087ff)
  • hydration: fix incorect mismatch warning for option with non-string value and inner text (d16a213)
  • reactivity: re-fix #​10114 (#​10123) (c2b274a)
  • runtime-core: should not warn out-of-render slot fn usage when mounting another app in setup (#​10125) (6fa33e6), closes #​10124
Performance Improvements
  • templateRef: avoid double render when using template ref on v-for (de4d2e2), closes #​9908
  • v-model: optimize v-model multiple select w/ large lists (2ffb956), closes #​10014
vuejs/test-utils (@​vue/test-utils)

v2.4.4

Compare Source

What's Changed

New Contributors

Full Changelog: vuejs/test-utils@v2.4.3...v2.4.4

evanw/esbuild (esbuild)

v0.20.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

  • Work around API deprecations in Deno 1.40.x (#​3609, #​3611)

    Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

    Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

  • Reorder implicit file extensions within node_modules (#​3341, #​3608)

    In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

    With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

    Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

v0.19.12

Compare Source

  • The "preserve" JSX mode now preserves JSX text verbatim (#​3605)

    The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).

    Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:

    // Original code
    let el =
      <a href={'/'} title='&apos;&quot;'> some text
        {foo}
          more text </a>
    
    // Old output (with --loader=jsx --jsx=preserve)
    let el = <a href="/" title={`'"`}>
      {" some text"}
      {foo}
      {"more text "}
    </a>;
    
    // New output (with --loader=jsx --jsx=preserve)
    let el = <a href={"/"} title='&apos;&quot;'> some text
        {foo}
          more text </a>;
  • Allow JSX elements as JSX attribute values

    JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with {...}. It looks like this:

    let el = <div data-ab=<><a/><b/></>/>;

    I think I originally didn't implement it even though it's part of the JSX specification because it previously didn't work in TypeScript (and potentially also in Babel?). However, support for it was silently added in TypeScript 4.8 without me noticing and Babel has also since fixed their bugs regarding this feature. So I'm adding it to esbuild too now that I know it's widely supported.

    Keep in mind that there is some ongoing discussion about removing this feature from JSX. I agree that the syntax seems out of place (it does away with the elegance of "JSX is basically just XML with {...} escapes" for something arguably harder to read, which doesn't seem like a good trade-off), but it's in the specification and TypeScript and Babel both implement it so I'm going to have esbuild implement it too. However, I reserve the right to remove it from esbuild if it's ever removed from the specification in the future. So use it with caution.

  • Fix a bug with TypeScript type parsing (#​3574)

    This release fixes a bug with esbuild's TypeScript parser where a conditional type containing a union type that ends with an infer type that ends with a constraint could fail to parse. This was caused by the "don't parse a conditional type" flag not getting passed through the union type parser. Here's an example of valid TypeScript code that previously failed to parse correctly:

    type InferUnion<T> = T extends { a: infer U extends number } | infer U extends number ? U : never
capricorn86/happy-dom (happy-dom)

v13.3.8

Compare Source

👷‍♂️ Patch fixes

v13.3.7

Compare Source

👷‍♂️ Patch fixes
  • Removes validation of PR commit messages from Github workflow as it will fallback to patch version anyway - By @​capricorn86 in task #​1249

v13.3.6

Compare Source

👷‍♂️ Patch fixes
  • Adds support for PR username in release notes if it is not possible to retrieve Github username based on commit email - By @​capricorn86 in task #​1247

v13.3.5

Compare Source

🎨 Features
👷‍♂️ Patch fixes
  • Fixes problem with calculating next version by updating the package "happy-conventional-commit" - By @​capricorn86 in task #​1244

v13.3.4

Compare Source

👷‍♂️ Patch fixes

v13.3.3

[Compare Source](https://togithub.co


Configuration

📅 Schedule: Branch creation - "every weekend after 4am" (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. View repository job log here.

@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 5 times, most recently from b510b6d to 32b89d8 Compare February 2, 2024 17:08
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 3 times, most recently from 5bdd645 to 063552e Compare February 14, 2024 10:56
@renovate renovate bot changed the title chore(deps): update all dependencies (non-major) fix(deps): update all dependencies (non-major) Feb 14, 2024
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 3 times, most recently from 2b6804b to 4736ec7 Compare February 15, 2024 12:19
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch from 4736ec7 to 438bf07 Compare February 15, 2024 12:45
Copy link
Contributor Author

renovate bot commented Feb 15, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@BalbinaK BalbinaK merged commit c2b2131 into next Feb 15, 2024
3 checks passed
@BalbinaK BalbinaK deleted the renovate/all-dependencies-(non-major) branch February 15, 2024 13:09
github-actions bot pushed a commit that referenced this pull request Feb 15, 2024
## [1.2.4-next.6](v1.2.4-next.5...v1.2.4-next.6) (2024-02-15)

### Bug Fixes

* **deps:** update all dependencies (non-major) ([#132](#132)) ([c2b2131](c2b2131))
github-actions bot pushed a commit that referenced this pull request Feb 15, 2024
## [1.2.4](v1.2.3...v1.2.4) (2024-02-15)

### Bug Fixes

* **deps:** update all dependencies (non-major) ([#132](#132)) ([c2b2131](c2b2131))
* **deps:** update dependency scroll-doctor to v2 ([#134](#134)) ([7e7e919](7e7e919))
* Remove redundant component css class from Modal ([#137](#137)) ([3d783f9](3d783f9))
* rename deleted icons after @warp-ds/icons update to 2.0.0 ([#136](#136)) ([e9ad066](e9ad066))
* replace letter x with icon close ([#129](#129)) ([56763e5](56763e5))
* Slider active track disabled state fix ([#139](#139)) ([a756c4c](a756c4c))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant