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

fix(deps): update external major (major) #2

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

fix(deps): update external major (major) #2

wants to merge 1 commit into from
+2,502 −2,417

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 8, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@types/react (source) ^18.0.24 -> ^19.0.0 age adoption passing confidence devDependencies major
@types/react-dom (source) ^18.0.8 -> ^19.0.0 age adoption passing confidence devDependencies major
@vitejs/plugin-react (source) ^2.2.0 -> ^4.0.0 age adoption passing confidence devDependencies major
actions/checkout v3 -> v4 age adoption passing confidence action major
actions/setup-node v3 -> v4 age adoption passing confidence action major
chai (source) 4.3.6 -> 5.1.2 age adoption passing confidence devDependencies major
jsdom ^20.0.3 -> ^26.0.0 age adoption passing confidence dependencies major
react (source) ^18.2.0 -> ^19.0.0 age adoption passing confidence dependencies major
react-dom (source) ^18.2.0 -> ^19.0.0 age adoption passing confidence dependencies major
rimraf ^3.0.2 -> ^6.0.0 age adoption passing confidence devDependencies major
sinon (source) 14.0.1 -> 19.0.2 age adoption passing confidence devDependencies major
stylelint (source) 14.13.0 -> 16.13.2 age adoption passing confidence devDependencies major
stylelint-config-standard 25.0.0 -> 37.0.0 age adoption passing confidence devDependencies major
vite (source) ^3.2.3 -> ^6.0.0 age adoption passing confidence devDependencies major
webpack-cli (source) ^5.0.1 -> ^6.0.0 age adoption passing confidence devDependencies major
wrangler (source) 2.5.0 -> 3.103.2 age adoption passing confidence devDependencies major

Release Notes

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

v4.3.4

Compare Source

Add Vite 6 to peerDependencies range

Vite 6 is highly backward compatible, not much to add!

Force Babel to output spec compliant import attributes #​386

The default was an old spec (with type: "json"). We now enforce spec compliant (with { type: "json" })

v4.3.3

Compare Source

React Compiler runtimeModule option removed

React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.

When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.

The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.

Here is the configuration to use the compiler with React 18 and correct source maps in development:

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

  return {
    plugins: [react({ babel: { plugins: babelPlugins } })],
  }
})

v4.3.2

Compare Source

Ignore directive sourcemap error #​369

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

v3.0.0

Compare Source

actions/checkout (actions/checkout)

v4

Compare Source

actions/setup-node (actions/setup-node)

v4

Compare Source

chaijs/chai (chai)

v5.1.2

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.1.1...v5.1.2

v5.1.1

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.1.0...v5.1.1

v5.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.0.3...v5.1.0

v5.0.3

Compare Source

Fix bad v5.0.2 publish.

Full Changelog: chaijs/chai@v5.0.2...v5.0.3

v5.0.2

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.0.1...v5.0.2

v5.0.0

Compare Source

BREAKING CHANGES

  • Chai now only supports EcmaScript Modules (ESM). This means your tests will need to either have import {...} from 'chai' or import('chai'). require('chai') will cause failures in nodejs. If you're using ESM and seeing failures, it may be due to a bundler or transpiler which is incorrectly converting import statements into require calls.
  • Dropped support for Internet Explorer.
  • Dropped support for NodeJS < 18.
  • Minimum supported browsers are now Firefox 100, Safari 14.1, Chrome 100, Edge 100. Support for browsers prior to these versions is "best effort" (bug reports on older browsers will be assessed individually and may be marked as wontfix).

What's Changed

New Contributors

Full Changelog: chaijs/chai@4.3.1...v5.0.0

v4.5.0

Compare Source

v4.4.1

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.4.0...v4.4.1

v4.4.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.3.10...v4.4.0

v4.3.10

Compare Source

This release simply bumps all dependencies to their latest non-breaking versions.

What's Changed

Full Changelog: chaijs/chai@v4.3.9...v4.3.10

v4.3.9

Compare Source

Upgrade dependencies.

This release upgrades dependencies to address CVE-2023-43646 where a large function name can cause "catastrophic backtracking" (aka ReDOS attack) which can cause the test suite to hang.

Full Changelog: chaijs/chai@v4.3.8...v4.3.9

v4.3.8

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v4.3.7...v4.3.8

v4.3.7

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.3.6...v4.3.7

jsdom/jsdom (jsdom)

v26.0.0

Compare Source

Breaking change: canvas peer dependency requirement has been upgraded from v2 to v3. (sebastianwachter)

Other changes:

  • Added AbortSignal.any(). (jdbevan)
  • Added initial support for form-associated custom elements, in particular making them labelable and supporting the ElementInternals labels property. The form-associated callbacks are not yet supported. (hesxenon)
  • Updated whatwg-url, adding support for URL.parse().
  • Updated cssstyle and rrweb-cssom, to improve CSS parsing capabilities.
  • Updated nwsapi, improving CSS selector matching.
  • Updated parse5, fixing a bug around <noframes> elements and HTML entity decoding.
  • Fixed JSDOM.fromURL() to properly reject the returned promise if the server redirects to an invalid URL, instead of causing an uncaught exception.

v25.0.1

Compare Source

  • Updated dependencies, notably tough-cookie, which no longer prints a deprecation warning.

v25.0.0

Compare Source

This major release changes the prototype of a jsdom's EventTarget.prototype to point to the Object.prototype inside the jsdom, instead of pointing to the Node.js Object.prototype. Thus, the prototype chain of Window stays entirely within the jsdom, never crossing over into the Node.js realm.

This only occurs when runScripts is set to non-default values of "dangerously" or "outside-only", as with the default value, there is no separate Object.prototype inside the jsdom.

This will likely not impact many programs, but could cause some changes in instanceof behavior, and so out of an abundance of caution, we're releasing it as a new major version.

v24.1.3

Compare Source

  • Fixed calls to postMessage() that were done as a bare property (i.e., postMessage() instead of window.postMessage()).

v24.1.2

Compare Source

  • Fixed an issue with the in operator applied to EventTarget methods, e.g. 'addEventListener' in window, which only appeared in Node.js ≥22.5.0. (legendecas)
  • Fixed the events fired by blur(): it no longer fires focus and focusin on the Document, and blur and focusout no longer have their relatedTarget property set. (asamuzaK)

v24.1.1

Compare Source

  • Fixed selection methods to trigger the selectionchange event on the Document object. (piotr-oles)

v24.1.0

Compare Source

  • Added the getSetCookie() method to the Headers class. (ushiboy)
  • Fixed the creation and parsing of elements with names from Object.prototype, like "constructor" or "toString".
  • Updated rweb-cssom, which can now parse additional CSS constructs.

v24.0.0

Compare Source

This release reverts our selector engine back to nwsapi. As discussed in #​3659, the performance regressions from @asamuzakjp/dom-selector turned out to be higher than anticipated. In the future, we can revisit @asamuzakjp/dom-selector after it reaches nwsapi's performance on the two real-world benchmarks provided by the community.

Since reverting to nwsapi causes several functionality regressions, e.g. removing :has() support, we've decided to make this a major version.

Additionally:

  • Small fixes to edge-case behavior of the following properties: input.maxLength, input.minLength, input.size, progress.max, tableCell.colSpan, tableCell.rowSpan, tableCol.span, textArea.cols, textArea.maxLength, textArea.minLength, textArea.rows.

v23.2.0

Compare Source

This release switches our CSS selector engine from nwsapi to @asamuzakjp/dom-selector. The new engine is more actively maintained, and supports many new selectors: see the package's documentation for the full list. It also works better with shadow trees.

There is a potential of a performance regression due to this change. In our stress test benchmark, which runs most of these 273 selectors against this 128 KiB document, the new engine completes the benchmark only 0.25x as fast. However, we're hopeful that in more moderate usage this will not be a significant issue. Any help speeding up @asamuzakjp/dom-selector is appreciated, and feel free to open an issue if this has had a significant impact on your project.

v23.1.0

Compare Source

  • Added an initial implementation of ElementInternals, including the shadowRoot getter and the string-valued ARIA properties. (zjffun)
  • Added the string-valued ARIA attribute-reflecting properties to Element.
  • Fixed history.pushState() and history.replaceState() to follow the latest specification, notably with regards to how they handle empty string inputs and what new URLs are possible.
  • Fixed the input.valueAsANumber setter to handle NaN correctly. (alexandertrefz)
  • Updated various dependencies, including cssstyle which contains several bug fixes.

v23.0.1

Compare Source

  • Fix incorrect canvas peer dependency.

v23.0.0

Compare Source

v22.1.0

Compare Source

  • Added crypto.randomUUID(). (jamesbvaughan)
  • Added DOMRect and DOMRectReadOnly.
  • Added AbortSignal.timeout().
  • Added abortSignal.throwIfAborted().
  • Added support for the submitter argument to the FormData constructor. (jenseng)
  • Improved getComputedStyle()'s results for color-based properties, to resolve named colors and attempt to provide initial inheritance support. (hoekz-wwt)
  • Updated Window's event handler properties (e.g. oncopy, ontouchstart, etc.) to reflect the latest list from the standard.
  • Fixed DOMParser-created documents to inherit their URL from the creating document.

v22.0.0

Compare Source

v21.1.2

Compare Source

  • Fixed setRangeText() used on <input> and <textarea> elements to calculate the new end index correctly. (pmstss)
  • Fixed pageX, pageY, offsetX, and offsetY on MouseEvents during dispatch. (jenseng)
  • Upgraded nwsapi to v2.2.4, bringing along various fixes to our selector engine.

v21.1.1

Compare Source

  • Fixed jsdom.reconfigure() to also adjust the URL as seen by the history API, so that e.g. history.replaceState(null, "") would not mess up the URL. (jdufresne)
  • Fixed location.hash = "" to leave any # in location.href.
  • Fixes a few bugs with CSS parsing by replacing cssom with rweb-cssom, since the latter is maintained. (seanparmelee)

v21.1.0

Compare Source

  • Added x, y, pageX, pageY, offsetX, and offsetY to MouseEvent. (jenseng, ViniciusFXavier)
  • Added support for unset with getComputedStyle(). (jsnajdr)
  • Added the submitter property to SubmitEvent. (jenseng)
  • Fixed MouseEvent's screenX and screenY to no longer coerce to integers, allowing fractional values. (jenseng)
  • Fixed formEl.submit() to not longer fire submit events. (jenseng)
  • Fixed stylesheets to no longer affect the document after their corresponding <link> is removed. (jsnajdr)
  • Fixed pointer-events to inherit when used with getComputedStyle(). (jnajdr)
  • Fixed <script> elements with no src="" to no longer fire load events. (t1ger2080)
  • Improved getComputedStyle() to cache its results, which should make it much faster. (jsnajdr)

v21.0.0

Compare Source

A potentially-breaking bug fix:

  • Fixed the window, document, location, and top properties of Window to be non-configurable. (ExE-Boss)

Other changes:

  • Added support for <input type=image> submitting forms. (jenseng)
  • Added the location setter to the Window object, which forwards to the location.href setter. Setting the URL is still only implemented for fragment navigations, however. (ExE-Boss)
  • Fixed defer="" <script> elements that are added after DOMContentLoaded to execute, instead of being skipped.
  • Fixed selectElement.selectedOptions being incorrect when optionElement.selected is set. This was a regression introduced in v20.0.1. Unfortunately this also reverts the performance improvement when appending <option> elements that was introduced then. (eps1lon)
  • Fixed the self, locationbar, menubar, personalbar, scrollbars, statusbar, toolbar, frames, parent, external, length, and screen properties of Window to be replaceable: that is, setting them will override their values, instead of having the new value be ignored. (ExE-Boss)
  • Fixed a few issues with JSDOM.fromURL() in the browser build of jsdom. (LungZeno)
facebook/react (react)

[`v

Configuration

📅 Schedule: Branch creation - "after 2pm on Monday" in timezone Europe/Zurich, 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.

@aem-code-sync AEM Code Sync
Copy link

aem-code-sync bot commented Apr 8, 2024 •
edited
Loading

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

  • Re-run PSI checks
  • Re-sync branch
Commits

@renovate renovate bot force-pushed the renovate-major-external-major branch from a46c829 to bcaea9b Compare April 13, 2024 08:58
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major April 13, 2024 08:58 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from bcaea9b to 5c2c072 Compare April 18, 2024 02:39
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major April 18, 2024 02:39 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 5c2c072 to c9ecc51 Compare April 19, 2024 17:45
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major April 19, 2024 17:45 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from c9ecc51 to d4bfda2 Compare April 23, 2024 23:23
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major April 23, 2024 23:23 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from d4bfda2 to ce5aae9 Compare April 24, 2024 17:49
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major April 24, 2024 17:49 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from 3997f49 to 85e715f Compare May 2, 2024 14:59
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 2, 2024 14:59 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 85e715f to b217049 Compare May 3, 2024 05:36
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 3, 2024 05:36 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from b217049 to 413bd00 Compare May 8, 2024 23:45
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 8, 2024 23:45 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 413bd00 to 6cc2915 Compare May 9, 2024 20:56
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 9, 2024 20:57 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 6cc2915 to bc3c7ce Compare May 13, 2024 21:03
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 13, 2024 21:03 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from 0ad1adc to 11ebf1f Compare May 25, 2024 05:00
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 25, 2024 05:00 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 11ebf1f to 3ad4936 Compare May 29, 2024 02:52
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 29, 2024 02:52 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 3ad4936 to 939a6ee Compare May 31, 2024 17:42
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major May 31, 2024 17:42 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 939a6ee to b85a18a Compare June 4, 2024 18:00
@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from 51a91e0 to 31e1465 Compare November 15, 2024 08:28
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major November 15, 2024 08:28 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 31e1465 to a7d5089 Compare November 21, 2024 02:51
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major November 21, 2024 02:51 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from a7d5089 to 1d39c89 Compare November 23, 2024 08:36
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major November 23, 2024 08:36 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 1d39c89 to abf044f Compare November 26, 2024 20:46
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major November 26, 2024 20:46 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from abf044f to 883fc81 Compare November 29, 2024 05:10
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major November 29, 2024 05:10 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 883fc81 to cca19db Compare December 5, 2024 23:50
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major December 5, 2024 23:50 Inactive
@renovate Renovate
Copy link
Author

renovate bot commented Dec 5, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: tools/litmus/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @adobe/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^19.0.0" from the root project
npm ERR!   peer react@">=15.0.0" from [email protected]
npm ERR!   node_modules/react-transition-group
npm ERR!     react-transition-group@"^2.2.0" from @react-spectrum/[email protected]
npm ERR!     node_modules/@react-spectrum/list
npm ERR!       @react-spectrum/list@"^3.2.0" from @adobe/[email protected]
npm ERR!       node_modules/@adobe/react-spectrum
npm ERR!         @adobe/react-spectrum@"^3.23.0" from the root project
npm ERR!     react-transition-group@"^2.2.0" from @react-spectrum/[email protected]
npm ERR!     node_modules/@react-spectrum/overlays
npm ERR!       @react-spectrum/overlays@"^4.0.0" from @adobe/[email protected]
npm ERR!       node_modules/@adobe/react-spectrum
npm ERR!         @adobe/react-spectrum@"^3.23.0" from the root project
npm ERR!       5 more (@react-spectrum/combobox, @react-spectrum/dialog, ...)
npm ERR!   1 more (react-dom)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || ^17.0.0-rc.1 || ^18.0.0" from @adobe/[email protected]
npm ERR! node_modules/@adobe/react-spectrum
npm ERR!   @adobe/react-spectrum@"^3.23.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.0 || ^17.0.0-rc.1 || ^18.0.0" from @adobe/[email protected]
npm ERR!   node_modules/@adobe/react-spectrum
npm ERR!     @adobe/react-spectrum@"^3.23.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2025-01-17T23_31_54_632Z-debug-0.log
File name: tools/simulate/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @adobe/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^19.0.0" from the root project
npm ERR!   peer react@">=15.0.0" from [email protected]
npm ERR!   node_modules/react-transition-group
npm ERR!     react-transition-group@"^2.2.0" from @react-spectrum/[email protected]
npm ERR!     node_modules/@react-spectrum/list
npm ERR!       @react-spectrum/list@"^3.2.0" from @adobe/[email protected]
npm ERR!       node_modules/@adobe/react-spectrum
npm ERR!         @adobe/react-spectrum@"^3.23.0" from the root project
npm ERR!     react-transition-group@"^2.2.0" from @react-spectrum/[email protected]
npm ERR!     node_modules/@react-spectrum/overlays
npm ERR!       @react-spectrum/overlays@"^4.0.0" from @adobe/[email protected]
npm ERR!       node_modules/@adobe/react-spectrum
npm ERR!         @adobe/react-spectrum@"^3.23.0" from the root project
npm ERR!       5 more (@react-spectrum/combobox, @react-spectrum/dialog, ...)
npm ERR!   1 more (react-dom)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || ^17.0.0-rc.1 || ^18.0.0" from @adobe/[email protected]
npm ERR! node_modules/@adobe/react-spectrum
npm ERR!   @adobe/react-spectrum@"^3.23.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.0 || ^17.0.0-rc.1 || ^18.0.0" from @adobe/[email protected]
npm ERR!   node_modules/@adobe/react-spectrum
npm ERR!     @adobe/react-spectrum@"^3.23.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2025-01-17T23_32_08_270Z-debug-0.log
File name: tools/personalization/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @adobe/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^19.0.0" from the root project
npm ERR!   peer react@">=15.0.0" from [email protected]
npm ERR!   node_modules/react-transition-group
npm ERR!     react-transition-group@"^2.2.0" from @react-spectrum/[email protected]
npm ERR!     node_modules/@react-spectrum/list
npm ERR!       @react-spectrum/list@"^3.2.0" from @adobe/[email protected]
npm ERR!       node_modules/@adobe/react-spectrum
npm ERR!         @adobe/react-spectrum@"^3.23.0" from the root project
npm ERR!     react-transition-group@"^2.2.0" from @react-spectrum/[email protected]
npm ERR!     node_modules/@react-spectrum/overlays
npm ERR!       @react-spectrum/overlays@"^4.0.0" from @adobe/[email protected]
npm ERR!       node_modules/@adobe/react-spectrum
npm ERR!         @adobe/react-spectrum@"^3.23.0" from the root project
npm ERR!       5 more (@react-spectrum/combobox, @react-spectrum/dialog, ...)
npm ERR!   1 more (react-dom)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.8.0 || ^17.0.0-rc.1 || ^18.0.0" from @adobe/[email protected]
npm ERR! node_modules/@adobe/react-spectrum
npm ERR!   @adobe/react-spectrum@"^3.23.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"^16.8.0 || ^17.0.0-rc.1 || ^18.0.0" from @adobe/[email protected]
npm ERR!   node_modules/@adobe/react-spectrum
npm ERR!     @adobe/react-spectrum@"^3.23.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2025-01-17T23_32_11_764Z-debug-0.log

@renovate renovate bot force-pushed the renovate-major-external-major branch 2 times, most recently from 7190d62 to 1f821da Compare December 11, 2024 17:15
@renovate renovate bot changed the title chore(deps): update external major (major) fix(deps): update external major (major) Dec 11, 2024
@renovate renovate bot force-pushed the renovate-major-external-major branch from 1f821da to b49e755 Compare December 16, 2024 01:30
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major December 16, 2024 01:30 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from b49e755 to 5e0526a Compare December 21, 2024 11:57
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major December 21, 2024 11:57 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 5e0526a to 1fcc582 Compare January 9, 2025 07:35
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major January 9, 2025 07:35 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 1fcc582 to e380ffc Compare January 11, 2025 03:07
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major January 11, 2025 03:07 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from e380ffc to 5ebc1a5 Compare January 16, 2025 07:52
@aem-code-sync aem-code-sync bot temporarily deployed to renovate-major-external-major January 16, 2025 07:52 Inactive
@renovate renovate bot force-pushed the renovate-major-external-major branch from 5ebc1a5 to 6c99218 Compare January 17, 2025 23:32
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.
0 participants