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

[BUMP] Update dependency happy-dom to v14 (pix-pro) - abandoned #680

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 21, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
happy-dom ^13.6.2 -> ^14.0.0 age adoption passing confidence

Release Notes

capricorn86/happy-dom (happy-dom)

v14.12.0

Compare Source

v14.11.4

Compare Source

v14.11.3

Compare Source

v14.11.2

Compare Source

v14.11.1

Compare Source

v14.11.0

Compare Source

🎨 Features

v14.10.3

Compare Source

👷‍♂️ Patch fixes
  • Adds check for if Window and MutationObserver has been destroyed when triggering listeners - By @​capricorn86 in task #​1436

v14.10.2

Compare Source

👷‍♂️ Patch fixes
  • HTMLAnchorElement, HTMLButtonElement, HTMLInputElement and HTMLLabelElement checked that click events triggering native behavior was of type PointerEvent, but should check that they are of type MouseEvent - By @​capricorn86 in task #​1397

v14.10.1

Compare Source

v14.10.0

Compare Source

🎨 Features
  • Adds support for Document.elementFromPoint() - By @​TreyVigus in task #​1400
    • The method will always return null as Happy DOM doesn't support rendering and can't calculate an element's position based on where it is rendered

v14.9.0

Compare Source

v14.8.3

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue related to Element.insertBefore() not removing comment node from previous ancestor - By @​mdafanasev in task #​1406

v14.8.2

Compare Source

v14.8.1

Compare Source

v14.8.0

Compare Source

🎨 Features

v14.7.1

Compare Source

👷‍♂️ Patch fixes

v14.7.0

Compare Source

v14.6.2

Compare Source

👷‍♂️ Patch fixes

v14.6.1

Compare Source

👷‍♂️ Patch fixes
  • Fixes bug where Document.createTextNode() didn't handle conversion of non-string values to string - By @​odanado in task #​1380
  • Adds support for throwing an exception when no argument is submitted to Document.createTextNode() - By @​odanado in task #​1380

v14.6.0

Compare Source

v14.5.2

Compare Source

v14.5.1

Compare Source

👷‍♂️ Patch fixes
  • Fixes problem with Document.defaultView not referring to the global object when using GlobalRegistrator - By @​capricorn86 in task #​1367

v14.5.0

Compare Source

🎨 Features
  • Adds support for handling "application/x-www-form-urlencoded" in Request.formData() - By @​tt-public in #​1379

v14.4.0

Compare Source

v14.3.10

Compare Source

👷‍♂️ Patch fixes
  • Fixes problem related to CSS properties not being used when defined after the CSS value - By @​capricorn86 in task #​1364

v14.3.9

Compare Source

👷‍♂️ Patch fixes

v14.3.8

Compare Source

👷‍♂️ Patch fixes
  • Fixes problem when the error for the invalid selectors :is and :where (without argument) was not handled correctly - By @​capricorn86 in task #​1352

v14.3.7

Compare Source

👷‍♂️ Patch fixes

v14.3.6

Compare Source

👷‍♂️ Patch fixes

v14.3.5

Compare Source

v14.3.4

Compare Source

v14.3.3

Compare Source

v14.3.2

Compare Source

👷‍♂️ Patch fixes

v14.3.1

Compare Source

v14.3.0

Compare Source

v14.2.1

Compare Source

v14.2.0

Compare Source

🎨 Features

v14.1.2

Compare Source

👷‍♂️ Patch fixes
  • Fixes problem with properties defined as getters and setters not being registered globally by Vitest - By @​capricorn86 in task #​1339
    • The problem occurred as Vitest is using Object.getOwnPropertyDescriptors(window) to read which properties to register globally, but getters and setters are defined on the prototype
    • To solve the problem, GlobalWindow now defines the properties on the instance when it is constructed

v14.1.1

Compare Source

v14.1.0

Compare Source

🎨 Features
  • Adds support for the setting handleDisabledFileLoadingAsSuccess, that can be used for triggering a "load" event instead of an "error" event when file loading is disabled - By @​capricorn86 in task #​1334

v14.0.0

Compare Source

💣 Breaking Changes
  • Removes interfaces for Node's, as they are no longer needed as newer versions of Typescript can handle circular dependencies - By @​capricorn86 in task #​1330

Configuration

📅 Schedule: Branch creation - "every 1 hour every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR has been generated by Mend Renovate. View repository job log here.

Copy link
Contributor Author

renovate bot commented Jun 21, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact 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: pix-pro/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nuxt/[email protected]
npm error Found: [email protected]
npm error node_modules/happy-dom
npm error   dev happy-dom@"^14.0.0" from the root project
npm error   peerOptional happy-dom@"*" from [email protected]
npm error   node_modules/vitest
npm error     dev vitest@"^1.3.1" from the root project
npm error     peerOptional vitest@"^0.34.6 || ^1.0.0" from @nuxt/[email protected]
npm error     node_modules/@nuxt/test-utils
npm error       dev @nuxt/test-utils@"^3.11.0" from the root project
npm error       1 more (vitest-environment-nuxt)
npm error
npm error Could not resolve dependency:
npm error peerOptional happy-dom@"^9.10.9 || ^10.0.0 || ^11.0.0 || ^12.0.0 || ^13.0.0" from @nuxt/[email protected]
npm error node_modules/@nuxt/test-utils
npm error   dev @nuxt/test-utils@"^3.11.0" from the root project
npm error   @nuxt/test-utils@">=3.9.0" from [email protected]
npm error   node_modules/vitest-environment-nuxt
npm error     vitest-environment-nuxt@"^1.0.0" from @nuxt/[email protected]
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/happy-dom
npm error   peerOptional happy-dom@"^9.10.9 || ^10.0.0 || ^11.0.0 || ^12.0.0 || ^13.0.0" from @nuxt/[email protected]
npm error   node_modules/@nuxt/test-utils
npm error     dev @nuxt/test-utils@"^3.11.0" from the root project
npm error     @nuxt/test-utils@">=3.9.0" from [email protected]
npm error     node_modules/vitest-environment-nuxt
npm error       vitest-environment-nuxt@"^1.0.0" from @nuxt/[email protected]
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-06-21T17_30_29_225Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-21T17_30_29_225Z-debug-0.log

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jun 21, 2024
@pix-bot-github
Copy link

Une fois les applications déployées, elles seront accessibles via les liens suivants :

Les variables d'environnement seront accessibles sur scalingo https://dashboard.scalingo.com/apps/osc-fr1/pix-site-review-pr680/environment

@renovate renovate bot changed the title [BUMP] Update dependency happy-dom to v14 (pix-pro) [BUMP] Update dependency happy-dom to v14 (pix-pro) - autoclosed Aug 5, 2024
@renovate renovate bot closed this Aug 5, 2024
@renovate renovate bot deleted the renovate/pix-pro-happy-dom-14.x branch August 5, 2024 10:31
@renovate renovate bot changed the title [BUMP] Update dependency happy-dom to v14 (pix-pro) - autoclosed [BUMP] Update dependency happy-dom to v14 (pix-pro) Aug 6, 2024
@renovate renovate bot restored the renovate/pix-pro-happy-dom-14.x branch August 6, 2024 09:36
@renovate renovate bot reopened this Aug 6, 2024
@pix-bot-github
Copy link

Une fois les applications déployées, elles seront accessibles via les liens suivants :

Les variables d'environnement seront accessibles sur scalingo https://dashboard.scalingo.com/apps/osc-fr1/pix-site-review-pr680/environment

Copy link
Contributor Author

renovate bot commented Sep 25, 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.

@renovate renovate bot changed the title [BUMP] Update dependency happy-dom to v14 (pix-pro) [BUMP] Update dependency happy-dom to v14 (pix-pro) - abandoned Nov 6, 2024
Copy link
Contributor Author

renovate bot commented Nov 6, 2024

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants