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

Update NPM packages #7996

Draft
wants to merge 4 commits into
base: trunk
Choose a base branch
from
Draft

Conversation

desrosj
Copy link
Contributor

@desrosj desrosj commented Dec 11, 2024

Trac ticket: https://core.trac.wordpress.org/ticket/62220


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

@desrosj desrosj self-assigned this Dec 11, 2024
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@ockham
Copy link
Contributor

ockham commented Dec 12, 2024

👋 @desrosj Are you planning to land this in the near future (i.e. well before WP 6.8 Beta 1)?

(FWIW, I'd love that, as I have a janitorial PR that requires a package update 😊)

@desrosj desrosj added the props-bot Adding this label triggers the Props Bot workflow for a PR. label Dec 12, 2024
@desrosj
Copy link
Contributor Author

desrosj commented Dec 12, 2024

@ockham I plan to merge this sometime next week! But it's not a high priority.

Is the concern a merge conflict? Or something else? Don't feel blocked to commit your PR if it's ready and I'll adjust. 😄

@ockham
Copy link
Contributor

ockham commented Dec 12, 2024

@ockham I plan to merge this sometime next week! But it's not a high priority.

Is the concern a merge conflict? Or something else? Don't feel blocked to commit your PR if it's ready and I'll adjust. 😄

Thank you, but I really can't land mine before a package update 😅 A while ago, I removed some now-obsolete functions from the Navigation block's PHP in Gutenberg. My PR moves -- or rather copies -- them to deprecated.php. But that means that they're colliding with the function declarations that still exist in Core's navigation.php -- until that file is updated by a package sync.

I hope that made sense. But again, not urgent at all -- any time before Beta 1 is fine 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
props-bot Adding this label triggers the Props Bot workflow for a PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants