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 the npm_and_yarn group across 1 directory with 4 updates #151

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 22, 2024

Bumps the npm_and_yarn group with 2 updates in the / directory: @wordpress/scripts and express.

Updates @wordpress/scripts from 27.9.0 to 30.3.0

Changelog

Sourced from @​wordpress/scripts's changelog.

30.3.0 (2024-10-17)

New Features

  • Add new build-blocks-manifest command to generate a PHP file containing block metadata from all block.json files in a project (#65866).

30.2.0 (2024-10-16)

30.1.0 (2024-10-03)

30.0.0 (2024-09-19)

Breaking Changes

  • Updated stylelint dependency to ^16.8.2 (#64828).
  • Switched default config from @wordpress/stylelint-config/scss to use @wordpress/stylelint-config/scss-stylistic to keep stylistic rules (#64828).

29.0.0 (2024-09-05)

Breaking Changes

  • Fixed the issue with having 5 high severity vulnerabilities by upgrading the puppeteer-core package to the latest major version ^23.1.0 (#64597).

Enhancements

  • Inlines CSS files imported from other CSS files before optimization in the build command (#61121).

Bug Fixes

  • Added chunk filename in webpack config to avoid reading stale files (#58176).

28.6.0 (2024-08-21)

28.5.0 (2024-08-07)

28.4.0 (2024-07-24)

New Features

  • Update webpack configuration for the build and start commands to automatically copy PHP files listed in the variations field of block.json files from the source to the build folder (#63098).

28.3.0 (2024-07-10)

28.2.0 (2024-06-26)

28.1.0 (2024-06-15)

28.0.0 (2024-05-31)

Breaking Changes

... (truncated)

Commits

Updates express from 4.19.2 to 4.21.1

Release notes

Sourced from express's releases.

4.21.1

What's Changed

Full Changelog: expressjs/express@4.21.0...4.21.1

4.21.0

What's Changed

New Contributors

Full Changelog: expressjs/express@4.20.0...4.21.0

4.20.0

What's Changed

Important

  • IMPORTANT: The default depth level for parsing URL-encoded data is now 32 (previously was Infinity)
  • Remove link renderization in html while using res.redirect

Other Changes

... (truncated)

Changelog

Sourced from express's changelog.

4.21.1 / 2024-10-08

4.21.0 / 2024-09-11

4.20.0 / 2024-09-10

  • deps: [email protected]
    • Remove link renderization in html while redirecting
  • deps: [email protected]
    • Remove link renderization in html while redirecting
  • deps: [email protected]
    • add depth option to customize the depth level in the parser
    • IMPORTANT: The default depth level for parsing URL-encoded data is now 32 (previously was Infinity)
  • Remove link renderization in html while using res.redirect
  • deps: [email protected]
    • Adds support for named matching groups in the routes using a regex
    • Adds backtracking protection to parameters without regexes defined
  • deps: encodeurl@~2.0.0
    • Removes encoding of \, |, and ^ to align better with URL spec
  • Deprecate passing options.maxAge and options.expires to res.clearCookie
    • Will be ignored in v5, clearCookie will set a cookie with an expires in the past to instruct clients to delete the cookie
Commits

Updates send from 0.18.0 to 0.19.0

Release notes

Sourced from send's releases.

0.19.0

What's Changed

New Contributors

Full Changelog: pillarjs/send@0.18.0...0.19.0

Changelog

Sourced from send's changelog.

0.19.0 / 2024-09-10

  • Remove link renderization in html while redirecting
Commits
Maintainer changes

This version was pushed to npm by ulisesgascon, a new releaser for send since your current version.


Updates serve-static from 1.15.0 to 1.16.2

Release notes

Sourced from serve-static's releases.

1.16.0

What's Changed

New Contributors

Full Changelog: expressjs/serve-static@v1.15.0...1.16.0

Changelog

Sourced from serve-static's changelog.

1.16.2 / 2024-09-11

  • deps: encodeurl@~2.0.0

1.16.1 / 2024-09-11

1.16.0 / 2024-09-10

  • Remove link renderization in html while redirecting
Commits
Maintainer changes

This version was pushed to npm by wesleytodd, a new releaser for serve-static since your current version.


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps the npm_and_yarn group with 2 updates in the / directory: [@wordpress/scripts](https://github.com/WordPress/gutenberg/tree/HEAD/packages/scripts) and [express](https://github.com/expressjs/express).


Updates `@wordpress/scripts` from 27.9.0 to 30.3.0
- [Release notes](https://github.com/WordPress/gutenberg/releases)
- [Changelog](https://github.com/WordPress/gutenberg/blob/trunk/packages/scripts/CHANGELOG.md)
- [Commits](https://github.com/WordPress/gutenberg/commits/@wordpress/[email protected]/packages/scripts)

Updates `express` from 4.19.2 to 4.21.1
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/4.21.1/History.md)
- [Commits](expressjs/express@4.19.2...4.21.1)

Updates `send` from 0.18.0 to 0.19.0
- [Release notes](https://github.com/pillarjs/send/releases)
- [Changelog](https://github.com/pillarjs/send/blob/master/HISTORY.md)
- [Commits](pillarjs/send@0.18.0...0.19.0)

Updates `serve-static` from 1.15.0 to 1.16.2
- [Release notes](https://github.com/expressjs/serve-static/releases)
- [Changelog](https://github.com/expressjs/serve-static/blob/v1.16.2/HISTORY.md)
- [Commits](expressjs/serve-static@v1.15.0...v1.16.2)

---
updated-dependencies:
- dependency-name: "@wordpress/scripts"
  dependency-type: direct:development
  dependency-group: npm_and_yarn
- dependency-name: express
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: send
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: serve-static
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from jeffpaul as a code owner October 22, 2024 23:27
@dependabot dependabot bot added the type:dependency An issue with a separate library that this project relies upon. label Oct 22, 2024
@dependabot dependabot bot requested a review from dkotter as a code owner October 22, 2024 23:27
@jeffpaul jeffpaul requested review from peterwilsoncc and removed request for dkotter and jeffpaul October 23, 2024 02:16
@jeffpaul jeffpaul added this to the 1.4.0 milestone Oct 23, 2024
@peterwilsoncc
Copy link
Contributor

I need to confirm but I think we can polyfill the JX Runtime with something like this for older versions of WP:

import { createElement, Fragment as ReactFragment } from 'react';

const jsx = ( element, props = {}, key = '' ) => {
	let children = [];
	if ( props.children ) {
		children = Array.isArray( props.children ) ? props.children : [ props.children ];
		delete props.children;
	}

	if ( key ) {
		props.key = key;
	}

	return createElement( element, props, ...children );
};

const jsxs = ( element, props = {}, key = '' ) => {
	return jsx( element, props, key );
}

const Fragment = ReactFragment;

globalThis.ReactJSXRuntime = globalThis.ReactJSXRuntime || { jsx, jsxs, Fragment };

Getting a logic check before I break everything though.

@jeffpaul
Copy link
Member

@peterwilsoncc any updates on this?

@peterwilsoncc
Copy link
Contributor

@dependabot rebase

Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 12, 2024

Superseded by #155.

@dependabot dependabot bot closed this Nov 12, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/npm_and_yarn-100044adbf branch November 12, 2024 04:19
@peterwilsoncc
Copy link
Contributor

@jeffpaul Apparently it's not quite as straight forward as I had hoped, there can be differences in how JSX works with different syntax, see WordPress/gutenberg#62202 (comment)

We can either use the Jetpack style fix and enqueue the JSX runtime and hope, or simply bump the requirements to 6.6 for the relevant plugins.

@jeffpaul
Copy link
Member

@peterwilsoncc I'm fine with bumping to 6.6 as minimum and just be at L-1 instead of L-2 for support policy for WP core on those specific plugins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:dependency An issue with a separate library that this project relies upon.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants