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 dependencies (major) #166

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update all dependencies (major) #166

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 1, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@testing-library/jest-dom ^5.16.5 -> ^6.0.0 age adoption passing confidence devDependencies major
@testing-library/react ^13.3.0 -> ^16.0.0 age adoption passing confidence devDependencies major
@vitejs/plugin-react (source) ^3.0.0 -> ^4.0.0 age adoption passing confidence devDependencies major
clsx ^1.2.1 -> ^2.0.0 age adoption passing confidence dependencies major
concurrently ^7.1.0 -> ^9.0.0 age adoption passing confidence dependencies major
flake8 (changelog) ==6.0.0 -> ==7.1.1 age adoption passing confidence major
lxml (source, changelog) ==4.9.2 -> ==5.3.0 age adoption passing confidence major
node 19 -> 22 age adoption passing confidence stage major
tenacity ==8.2.3 -> ==9.0.0 age adoption passing confidence major
typescript (source) ^4.6.4 -> ^5.0.0 age adoption passing confidence devDependencies major
ubuntu focal -> noble age adoption passing confidence final major
ubuntu focal -> noble age adoption passing confidence stage major

Release Notes

testing-library/jest-dom (@​testing-library/jest-dom)

v6.5.0

Compare Source

v6.4.8

Compare Source

v6.4.7

Compare Source

v6.4.6

Compare Source

Bug Fixes

v6.4.5

Compare Source

Bug Fixes

v6.4.4

Compare Source

v6.4.3

Compare Source

v6.4.2

Compare Source

Bug Fixes
  • Remove errant export of GetByRoleMatcher, fixing type checking in some TS configurations (#​575) (a93c0c4)

v6.4.1

Compare Source

Bug Fixes
  • Export type TestingLibraryMatchers from "./matchers" (#​576) (dd1c4dd)

v6.4.0

Compare Source

Features

v6.3.0

Compare Source

Features

v6.2.1

Compare Source

Bug Fixes
  • Standalone types for "./matchers" export and add Bun support (#​566) (5675b86)

v6.2.0

Compare Source

Features
  • toHaveAccessibleDescription supports aria-description (#​565) (1fb156c)

v6.1.6

Compare Source

Bug Fixes

v6.1.5

Compare Source

Bug Fixes

v6.1.4

Compare Source

Bug Fixes
  • upgrade @adobe/css-tools to 4.3.1 to address vulnerability (#​532) (44f1eab)

v6.1.3

Compare Source

Bug Fixes

v6.1.2

Compare Source

Bug Fixes

v6.1.1

Compare Source

Bug Fixes

v6.1.0

Compare Source

Features

v6.0.1

Compare Source

Bug Fixes
  • matchers type is making the global expect unsafe (#​513) (bdb34f1)

v6.0.0

Compare Source

Features
BREAKING CHANGES
  • Removes the extend-expect script. Users should use
    the default import path or one of the new test platform-specific
    paths to automatically extend the appropriate "expect" instance.

extend-expect was not documented in the Readme, so this change should
have minimal impact.

Users can now use the following import paths to automatically extend
"expect" for their chosen test platform:

For example:

import '@​testing-library/jest-dom/jest-globals'

Importing from one of the above paths will augment the appropriate
matcher interface for the given test platform, assuming the import
is done in a .ts file that is included in the user's tsconfig.json.

It's also (still) possible to import the matchers directly without
side effects:

import * as matchers from '@​testing-library/jest-dom/matchers'

  • Update kcd-scripts
  • Drop node < 14

v5.17.0

Compare Source

Features
  • New toHaveAccessibleErrorMessage better implementing the spec, deprecate toHaveErrorMessage (#​503) (d717c66)
testing-library/react-testing-library (@​testing-library/react)

v16.0.1

Compare Source

v16.0.0

Compare Source

Features
  • Move @testing-library/dom and @types/react-dom to peer dependencies (#​1305) (a4744fa)
BREAKING CHANGES
  • @testing-library/dom was moved to a peer dependency and needs to be explicitly installed. This reduces the chance of having conflicting versions of @testing-library/dom installed that frequently caused bugs when used with @testing-library/user-event. We will also be able to allow new versions of @testing-library/dom being used without a SemVer major release of @testing-library/react by just widening the peer dependency.
    @types/react-dom needs to be installed if you're typechecking files using @testing-library/react.

v15.0.7

Compare Source

v15.0.6

Compare Source

v15.0.5

Compare Source

v15.0.4

Compare Source

v15.0.3

Compare Source

Bug Fixes
  • Don't raise TypeScript errors when hydating document (#​1304) (067d0c6)

v15.0.2

Compare Source

v15.0.1

Compare Source

v15.0.0

Compare Source

v14.3.1

Compare Source

Bug Fixes

v14.3.0

Compare Source

v14.2.2

Compare Source

v14.2.1

Compare Source

Bug Fixes
  • Update types to support all possible react component return values (#​1272) (55e79c2)

v14.2.0

Compare Source

Features
  • add reactStrictMode option to enable strict mode render (#​1241) (0880eba)

v14.1.2

Compare Source

Bug Fixes

v14.1.1

Compare Source

Bug Fixes

v14.1.0

Compare Source

Features

v14.0.0

Compare Source

Bug Fixes
Features
BREAKING CHANGES

v13.4.0

Compare Source

Features
  • renderHook: allow passing of all render options to renderHook (#​1118) (27a9584)
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'.

v4.3.0

Compare Source

Fix support for React compiler

Don't set retainLines: true when the React compiler is used. This creates whitespace issues and the compiler is modifying the JSX too much to get correct line numbers after that. If you want to use the React compiler and get back correct line numbers for tools like vite-plugin-react-click-to-component to work, you should update your config to something like:

export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', {}]]
  if (command === 'serve') {
    babelPlugins.push(['@&#8203;babel/plugin-transform-react-jsx-development', {}])
  }

  return {
    plugins: [react({ babel: { plugins: babelPlugins } })],
  }
})
Support HMR for class components

This is a long overdue and should fix some issues people had with HMR when migrating from CRA.

v4.2.1

Compare Source

Remove generic parameter on Plugin to avoid type error with Rollup 4/Vite 5 and skipLibCheck: false.

I expect very few people to currently use this feature, but if you are extending the React plugin via api object, you can get back the typing of the hook by importing ViteReactPluginApi:

import type { Plugin } from 'vite'
import type { ViteReactPluginApi } from '@&#8203;vitejs/plugin-react'

export const somePlugin: Plugin = {
  name: 'some-plugin',
  api: {
    reactBabel: (babelConfig) => {
      babelConfig.plugins.push('some-babel-plugin')
    },
  } satisfies ViteReactPluginApi,
}

v4.2.0

Compare Source

Update peer dependency range to target Vite 5

There were no breaking change that impacted this plugin, so any combination of React plugins and Vite core version will work.

Align jsx runtime for optimized dependencies

This will only affect people using internal libraries that contains untranspiled JSX. This change aligns the optimizer with the source code and avoid issues when the published source don't have React in the scope.

Reminder: While being partially supported in Vite, publishing TS & JSX outside of internal libraries is highly discouraged.

v4.1.1

Compare Source

  • Enable retainLines to get correct line numbers for jsxDev (fix #​235)

v4.1.0

Compare Source

  • Add @types/babel__cores to dependencies (fix #​211)
  • Improve build perf when not using Babel plugins by lazy loading @babel/core #​212
  • Better invalidation message when an export is added & fix HMR for export of nullish values #​215
  • Include non-dev jsx runtime in optimizeDeps & support HMR for JS files using the non dev runtime #​224
  • The build output now contains a index.d.cts file so you don't get types errors when setting moduleResolution to node16 or nodenext in your tsconfig (we recommend using bundler which is more close to how Vite works)

v4.0.4

Compare Source

  • Fix #​198: Enable Babel if presets list is not empty

v4.0.3

Compare Source

  • Revert #​108: Remove throw when refresh runtime is loaded twice to enable usage in micro frontend apps. This was added to help fix setup usage, and this is not worth an annoying warning for others or a config parameter.

v4.0.2

Compare Source

  • Fix fast-refresh for files that are transformed into jsx (#​188)

v4.0.1

Compare Source

v4.0.0

Compare Source

This major version include a revamp of options:

  • include/exclude now allow to completely override the files processed by the plugin (#​122). This is more in line with other Rollup/Vite plugins and simplify the setup of enabling Fast Refresh for .mdx files. This can be done like this:
export default defineConfig({
  plugins: [
    { enforce: 'pre', ...mdx() },
    react({ include: /\.(mdx|js|jsx|ts|tsx)$/ }),
  ],
})

These changes also allow to apply Babel plugins on files outside Vite root (expect in node_modules), which improve support for monorepo (fix #​16).

With these changes, only the file extensions is used for filtering processed files and the query param fallback is removed.

  • fastRefresh is removed (#​122). This should be correctly activated by plugin without configuration.
  • jsxPure is removed. This is a niche use case that was just passing down the boolean to esbuild.jsxSideEffects. (#​129)

The support for React auto import whe using classic runtime is removed. This was prone to errors and added complexity for no good reason given the very wide support of automatic runtime nowadays. This migration path should be as simple as removing the runtime option from the config.

This release goes in hand with the upcoming Vite 4.3 release focusing on performances:

  • Cache plugin load (#​141)
  • Wrap dynamic import to speedup analysis (#​143)

Other notable changes:

  • Silence "use client" warning (#​144, fix #​137)
  • Fast Refresh is applied on JS files using automatic runtime (#​122, fix #​83)
  • Vite 4.2 is required as a peer dependency (#​128)
  • Avoid key collision in React refresh registration (a74dfef, fix #​116)
  • Throw when refresh runtime is loaded twice (#​108, fix #​101)
  • Don't force optimization of jsx-runtime (#​132)

v3.1.0

Compare Source

  • doc: add jsxImportSource option (38d71f6)
  • chore: bump release-scripts, typecheck package in CI, remove cache for eslint (9af763d)
  • fix: fast-refresh explain link (#​97) (6097795), closes #​97

v3.0.1

Compare Source

lukeed/clsx (clsx)

v2.1.1

Compare Source

Patches

Chores

  • Add licenses.dev badge: 684509c
    This service recursively analyzes entire dependency graphs to ensure that a package (or your project) is using permissive licenses. For example, here's a results table for polka@next and a larger astro example.

Full Changelog: lukeed/clsx@v2.1.0...v2.1.1

v2.1.0

Compare Source

Features

  • Add new clsx/lite submodule for string-only usage: 1a49142

    This is a 140b version of clsx that is ideal for Tailwind and/or React contexts, which typically follow this clsx usage pattern:

    clsx('foo bar', props.maybe && 'conditional classes', props.className);

    Important: This clsx/lite module ignores all non-string arguments and is therefore not a 1:1 replacement for clsx itself!

    import { clsx } from 'clsx';
import { clsx as lite } from 'clsx/lite';

// strings-only usage is identical
clsx('foo', null, 'bar', true && 'baz'); //=> "foo bar baz"
lite('foo', null, 'bar', true && 'baz'); //=> "foo bar baz"

// clsx/lite ignores all non-strings
clsx('foo', { a: true, b: false, c: true }); //=> "foo a c"
lite('foo', { a: true, b: false, c: true }); //=> "foo"

Full Changelog: lukeed/clsx@v2.0.1...v2.1.0

v2.0.1

Compare Source

Patches

  • (perf) Cache arguments.length & array.length for 6% performance gain (#​26): deff09b
    Adds 5 bytes (+2%) for ~3% avg performance gain
    Thank you @​jalalazimi

Chores

Full Changelog: lukeed/clsx@v2.0.0...v2.0.1

v2.0.0

Compare Source

Breaking

  • Add "exports" map for native ESM support (#​57): 3ec8e9f, 0949868
    Also supports TypeScript's node16/nodenext module resolution
    Maintains CommonJS support (with fixed TS definitions)
    Thank you @​remcohaszing~!

Chores

Full Changelog: lukeed/clsx@v1.2.1...v2.0.0

open-cli-tools/concurrently (concurrently)

v9.0.1

Compare Source

What's Changed

Full Changelog: open-cli-tools/concurrently@v9.0.0...v9.0.1

v9.0.0

Compare Source

v8.2.2

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v8.2.1...v8.2.2

v8.2.1

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v8.2.0...v8.2.1

v8.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v8.1.0...v8.2.0

v8.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v8.0.1...v8.1.0

v8.0.1

Compare Source

What's Changed

Full Changelog: open-cli-tools/concurrently@v8.0.0...v8.0.1

v8.0.0

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v7.6.0...v8.0.0

v7.6.0

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v7.5.0...v7.6.0

v7.5.0

Compare Source

What's Changed

Full Changelog: open-cli-tools/concurrently@v7.4.0...v7.5.0

v7.4.0

Compare Source

New Contributors

pycqa/flake8 (flake8)

v7.1.1

Compare Source

v7.1.0

Compare Source

v7.0.0

Compare Source

v6.1.0

Compare Source

lxml/lxml (lxml)

v5.3.0

Compare Source

==================

Features added

  • GH#421: Nested CDATA sections are no longer rejected but split on output
    to represent ]]> correctly.
    Patch by Gertjan Klein.

Bugs fixed

  • [LP#206

Configuration

📅 Schedule: Branch creation - "on the first day of january" (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 was generated by Mend Renovate. View the repository job log.

@webteam-app
Copy link

Demo starting at https://specs-canonical-com-166.demos.haus

@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from 7c5a0e5 to f6d0701 Compare January 8, 2024 10:27
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from 9671cb1 to c727e60 Compare January 28, 2024 08:51
@renovate renovate bot force-pushed the renovate/major-all branch 3 times, most recently from c9f39cd to db01f9b Compare April 2, 2024 18:19
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from ae8a055 to a97d1c0 Compare April 26, 2024 18:45
@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 955f7fb to 792601d Compare August 4, 2024 22:14
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
@webteam-app