Skip to content

Release/v1.2.0#98

Open
geck1942 wants to merge 251 commits intodevelopmentfrom
release/v1.2.0
Open

Release/v1.2.0#98
geck1942 wants to merge 251 commits intodevelopmentfrom
release/v1.2.0

Conversation

@geck1942
Copy link
Contributor

@geck1942 geck1942 commented Aug 27, 2025

🚀 Major Version Updates

  • WordPress 6.8: Updated WordPress core and related dependencies (c0cd14c)
  • Node.js 22: Upgraded to Node.js v22 with updated CI/CD configurations (8af2282)
  • Next.js 15 + React 19: Updated to Next.js 15 and React 19 with all package dependencies (62b7163)

🐛 Compatibility Fixes

  • Fixed patterns and child blocks in Gutenberg inserter after WordPress update (a0f7f60)
  • Resolved WordPress 6.8 compatibility issues (1f8637b)
  • Fixed Next.js components rendering inside WordPress Editor (0674b6a)
  • Improved inner blocks and lists styling (91fe946)

✨ Enhancements

  • Added cache option to fetchAPI parameters (bba5069)
  • Enhanced Vercel deployment with CLI integration (97dc5fa)
  • Improved block whitelisting functionality (11c57f7)
  • Passing tests on PR
  • Documentation about tests and automation

🐛 Issues fixing

geck1942 added 30 commits May 8, 2025 15:14
- guthub develop PR workflow + actions
Copy link
Contributor

@kuuak kuuak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to update next version in readme file

- Next.js 14 with App Router and React Server Components

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have an error from the begining of a project setup. on npm install

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @wordpress/components@30.1.0
npm error Found: react@18.3.1
npm error node_modules/@wordpress/components/node_modules/react
npm error   peer react@">=16.8.0" from @floating-ui/react-dom@2.0.8
npm error   node_modules/@wordpress/components/node_modules/@floating-ui/react-dom
npm error     @floating-ui/react-dom@"2.0.8" from @wordpress/components@30.1.0
npm error     node_modules/@wordpress/components
npm error       dev @wordpress/components@"^30.0.0" from the root project
npm error   react@"^18.3.0" from @wordpress/element@6.28.0
npm error   node_modules/@wordpress/components/node_modules/@wordpress/element
npm error     @wordpress/element@"^6.28.0" from @wordpress/components@30.1.0
npm error     node_modules/@wordpress/components
npm error       dev @wordpress/components@"^30.0.0" from the root project
npm error     @wordpress/element@"^6.28.0" from @wordpress/icons@10.28.0
npm error     node_modules/@wordpress/components/node_modules/@wordpress/icons
npm error       @wordpress/icons@"^10.28.0" from @wordpress/components@30.1.0
npm error       node_modules/@wordpress/components
npm error         dev @wordpress/components@"^30.0.0" from the root project
npm error     1 more (@wordpress/primitives)
npm error   2 more (@wordpress/primitives, react-dom)
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0" from @wordpress/components@30.1.0
npm error node_modules/@wordpress/components
npm error   dev @wordpress/components@"^30.0.0" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peer react@"^18.0.0" from @wordpress/components@30.1.0
npm error   node_modules/@wordpress/components
npm error     dev @wordpress/components@"^30.0.0" from the root project
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 /Users/work/.npm/_logs/2025-09-01T09_18_29_846Z-eresolve-report.txt
npm error A complete log of this run can be found in: /Users/work/.npm/_logs/2025-09-01T09_18_29_846Z-debug-0.log

@github-actions
Copy link

github-actions bot commented Sep 1, 2025

End to end Tests Failed

To view the video recordings:

  • Go to the "Summary" tab of this workflow to Download and extract the "test-failure-videos" artifact.
  • Or find the link to the file in the action logs

Copy link
Contributor

@kuuak kuuak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are a few blocks not working in the storybook

Copy link
Contributor

@kuuak kuuak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hydration error in newly created project

Capture d’écran 2025-09-01 à 14 04 31

@github-actions
Copy link

github-actions bot commented Sep 1, 2025

End to end Tests Failed

To view the video recordings:

  • Go to the "Summary" tab of this workflow to Download and extract the "test-failure-videos" artifact.
  • Or find the link to the file in the action logs

- removed composer doc unsynced warning
…perhuit-agency/superstack into release/v1.2.0
@kuuak
Copy link
Contributor

kuuak commented Sep 8, 2025

That would be nice to fix this issue #99 in this release as well

@github-actions
Copy link

github-actions bot commented Sep 8, 2025

End to end Tests Failed

To view the video recordings:

  • Go to the "Summary" tab of this workflow to Download and extract the "test-failure-videos" artifact.
  • Or find the link to the file in the action logs

1 similar comment
@github-actions
Copy link

github-actions bot commented Sep 9, 2025

End to end Tests Failed

To view the video recordings:

  • Go to the "Summary" tab of this workflow to Download and extract the "test-failure-videos" artifact.
  • Or find the link to the file in the action logs

@github-actions
Copy link

End to end Tests Failed

To view the video recordings:

  • Go to the "Summary" tab of this workflow to Download and extract the "test-failure-videos" artifact.
  • Or find the link to the file in the action logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants