Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core.
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: jacobcassidy <jacobcassidy@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

The older version of sass-loader is using a legacy API that is coming to end-of-life. See https://sass-lang.com/documentation/breaking-changes/legacy-js-api/.

The @wordpress/scripts build process also shows multiple warnings every time it runs when sass files exist. This update removes them.

This was fixed with #67572. Tested with @wordpress/scripts@30.6.2-next.a9f418477.0. The stable version is expected to be published to npm on Wednesday. sass could still get enforced to more recent version in @wordpress/scripts and in Gutenberg, but it would be a complex warnings as there were many deprecations introduced that need to be addressed in the project.

Do you plan to continue working on this PR?

@gziolo I'm overloaded right now, so I don't plan to continue working on this anytime soon.

Do you want me to close the related WP PRs that I am no longer actively working on?

I'm overloaded right now, so I don't plan to continue working on this anytime soon.

That's fair. Thank you for helping with these efforts 🙇🏻‍♂️

I'll close this PR. Let me quickly check your other PRs to see whether we can move forward something 😄