#61692 closed defect (bug) (fixed)
Editor: Update packages for 6.6.1
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 6.6.1 | Priority: | normal |
Severity: | normal | Version: | 6.6 |
Component: | Editor | Keywords: | has-patch commit dev-reviewed fixed-major |
Focuses: | Cc: |
Change History (15)
This ticket was mentioned in PR #7057 on WordPress/wordpress-develop by @ellatrix.
7 months ago
#1
- Keywords has-patch added
#3
@
7 months ago
- Keywords commit added
Patch: https://github.com/WordPress/wordpress-develop/pull/7057
✅ Packages and their version changes match https://github.com/WordPress/gutenberg/commit/5c1d6bb774e6f78f0bbd4cdc85c4a7087da2f8a0
✅ Includes all fixes scrubbed earlier today.
✅ Tested locally - nothing in the server logs or browser console.
LGTM for commit ✅
Prepping commit now.
@hellofromTonya commented on PR #7057:
7 months ago
#5
Committed via https://core.trac.wordpress.org/changeset/58757.
#6
@
7 months ago
- Keywords dev-feedback added
- Resolution fixed deleted
- Status changed from closed to reopened
Reopening for 2nd committer sign-off to backport [58757] to the 6.6 branch for 6.6.1.
#7
follow-up:
↓ 8
@
7 months ago
There are multiple PR that contain PHP code that do not seem to be ported.
Examples
https://github.com/WordPress/gutenberg/pull/63436/
https://github.com/WordPress/gutenberg/pull/63637
Should these changes be manually ported?
@hellofromTonya @ellatrix
#8
in reply to:
↑ 7
@
7 months ago
Replying to spacedmonkey:
There are multiple PR that contain PHP code that do not seem to be ported.
Examples
https://github.com/WordPress/gutenberg/pull/63436/
https://github.com/WordPress/gutenberg/pull/63637
Should these changes be manually ported?
These were handled in separate tickets (referenced in the See
):
- https://github.com/WordPress/gutenberg/pull/63637 is tracked in #61660 and #61630 and committed to 6.6 branch by r58751.
- https://github.com/WordPress/gutenberg/pull/63436/ is tracked in #61656. It's been committed to
trunk
via r58750, but waiting to do the backport to 6.6 branch after this package update gets backported (to confirm the bug is fixed).
#9
@
7 months ago
Also just double-checked all of the other fixes. Only those 2 mentioned have PHP changes. Are you seeing others @spacedmonkey?
Trac ticket: https://core.trac.wordpress.org/ticket/61692