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 graphiql packages #2043

Merged
merged 1 commit into from
Jan 12, 2025
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 12, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
graphiql (source) 3.7.2 -> 3.8.3 age adoption passing confidence
preact (source) 10.24.3 -> 10.25.4 age adoption passing confidence

Release Notes

graphql/graphiql (graphiql)

v3.8.3

Compare Source

Patch Changes

v3.8.2

Compare Source

Patch Changes

v3.8.1

Compare Source

Patch Changes

v3.8.0

Compare Source

Minor Changes
Patch Changes
preactjs/preact (preact)

v10.25.4

Compare Source

Types

Fixes

v10.25.3

Compare Source

Fixes

Types

v10.25.2

Compare Source

Notable
Revert unkeyed no-search (#​4604, thanks @​JoviDeCroock)

We noticed that there's a few unpleasant scenario's that could form from this change, we wanted to be on the safe side here and revert this for the time being. if you run into issues with swapping components placement wise in a list use the key property.

Fixes
Types
Performance
Maintenance

v10.25.1

Compare Source

Fixes

Types

Maintenance

v10.25.0

Compare Source

Features

Move per-element type interfaces into core and more strictly type IntrinsicElements (#​4546, thanks @​rschristian)

This adds per-element typings for every DOM-node type, this means that our types might become slightly stricter when you are using DOM attributes/properties where they are not allowed, an example of this might be <div src="x" />.

If you notice any issues when upgrading tell us about them, we can evaluate whether we have missed a case.

Recreate unkeyed functional components when they change position. (#​4550, thanks @​JoviDeCroock)

This is a long time bugfix, when we have elements that look like

return (
	{condition ? <Element /> : null}
	{condition ? null : <Element />
)

We would reuse the state of the first VNode to render the second one when the condition switches. When you are using key, this issue was not present.

Support { handleEvent() {} } object interface as a listener (#​4538, thanks @​lilnasy)

We've added support for attaching object/class event-handlers

let handler = {
	onclick,
	handleEvent() {
		this.onclick()
	}
}

<div onClick={handler} />

Fixes

Maintenance


Configuration

📅 Schedule: Branch creation - "on the 12th day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jan 12, 2025
@renovate renovate bot force-pushed the renovate/graphiql-packages branch from 2f17414 to 1289201 Compare January 12, 2025 05:38
@renovate renovate bot merged commit 29d028a into master Jan 12, 2025
7 checks passed
@renovate renovate bot deleted the renovate/graphiql-packages branch January 12, 2025 09:38
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 javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants