Cherry-pick PRs for WP 7.1.1 by draganescu · Pull Request #82383 · WordPress/gutenberg

draganescu · 2026-09-03T11:59:40Z

Core ticket: https://core.trac.wordpress.org/ticket/66037

WordPress 7.1.1 is scheduled to be released on September 17th, and 7.1.1 RC1 is scheduled to be released on Semptember 10th. In preparation for that, this PR backports the PRs with the Backport to WP Minor Release label to the wp/7.1 branch.

cc @adamsilverstein, @adrianduffell

Caution

Personal note: Be sure to change to "Rebase and merge" not the default "Squash and merge" as this allows for a full history of commits.
https://developer.wordpress.org/block-editor/contributors/code/release/package-release-and-core-updates/#:~:text=Merge%20the%20Pull%20Request%20using%20the%20%E2%80%9CRebase%20and%20Merge%E2%80%9D%20button%20to%20keep%20the%20history%20of%20the%20commits.

The following PRs are included in this PR:

The cherry-pick of #82011 needed a one-line test adaptation on wp/7.1 (fac03fe): the empty canvas is role=button there because #81231 is not on the branch.

The cherry-pick of #81947 (e2a9c8d) also needed adapting, since wp/7.1 still runs Jest and its attachments controller has diverged from trunk.

Claude did the cherry-pick, its notes on what changed:

The two new editor unit tests and the mock added to the media-finalize test were written for Vitest on trunk. On this branch they are the same tests in Jest form.

The finalize_item() re-read of the post was inserted by hand into the branch's controller, which has none of the sub-size provenance code around it on trunk. The PHP tests apply as they are.

The cherry-pick of #82249 (b3acbb9) also needed adapting: wp/7.1 has neither the sharded performance workflow nor .github/setup-npm and the dev/build tsconfig split, and it pins Playwright 1.61/Jest 29, so the workflow changes were ported onto the branch's job layout and the tooling kept on the branch's dependency lines (details in the commit message, plus follow-ups 5ea23e4 and 018ee84).

The cherry-pick of #82265 (3f82d42) needed the same Jest treatment. Claude handled that one; in its words:

The two unit test files and the e2e spec are the trunk versions with vi.mock/vi.fn turned back into jest.mock/jest.fn; HeicUnsupportedError stays real via jest.requireActual so the instanceof branch is exercised. All 25 upload-media suites pass on the branch.

The following PRs have not been merged yet, and therefore not cherry-picked:

Global Styles: Retain responsive styles in block style variation partials #82403 @guzel

PHP changes needing Core patches

Three of the included PRs carry PHP changes that do not travel through the package build and need to land in wordpress-develop's 7.1 branch for 7.1.1 (tracked by their backport-changelog/7.1 entries):

Block Supports: Bail early in state styles when a block has no style attribute #81908 → committed as changeset 63474
Fix: Restore layout styles for block style variations #82335 → committed as [changeset 63523] (https://core.trac.wordpress.org/changeset/63523)
Editor: Store the finalize response as the attachment record #81947 → commited as [changeset 63572]

The package update itself is staged as WordPress/wordpress-develop#13422 (draft), to be re-pinned to the wp/7.1 tip once this PR is rebase-merged.

How to test

Refer to the commit history to ensure your PR is cherry-picked correctly.
Verify that the bug is fixed as expected.
Overall, smoke test for any critical errors.

Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: tellthemachines <isabel_brison@git.wordpress.org>

…nage_options cap (#81813) * Resolve the preloading correctly based on the capabilities * Remove read cap check and fetch global style for non-admin using view context

…82046) Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org> Co-authored-by: andrewserong <andrewserong@git.wordpress.org>

* Accordion Panel: Reset padding-block when panel is hidden. When the accordion content style was changed to support in-browser search via `hidden="until-found"` (#74744), the browser applies `content-visibility: hidden`. Because `content-visibility: hidden` hides contents without removing the container box model, any user- or theme-defined padding on the Accordion Panel block produced an empty gap below the title when the accordion was closed. This resets `padding-block: 0 !important` on `.wp-block-accordion-panel[hidden]` so the closed panel occupies no vertical space while preserving the full padding when the panel is open. Fixes #65900 (Trac #65900). * Reset borders, box shadows, and padding on hidden accordion panel. Addresses review feedback by ensuring borders and box shadows are also reset when the accordion panel is hidden, along with padding. * Add changelog entry for Accordion Panel hidden padding fix --------- Co-authored-by: wprashed <wprashed@git.wordpress.org> Co-authored-by: t-hamano <wildworks@git.wordpress.org>

…1964) Unlinked contributors: YamabikoLab. Co-authored-by: shail-mehta <shailu25@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: andrewserong <andrewserong@git.wordpress.org>

Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org> Co-authored-by: andrewserong <andrewserong@git.wordpress.org> Co-authored-by: jasmussen <joen@git.wordpress.org> Co-authored-by: aaronjorbin <jorbin@git.wordpress.org>

@nosilver4u

Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org> Co-authored-by: swissspidy <swissspidy@git.wordpress.org> Co-authored-by: kleisauke <kleisauke@git.wordpress.org> Co-authored-by: t-hamano <wildworks@git.wordpress.org> Props to @nosilver4u for the original report.

…82316) * Image block: sync / update image size settings when applying a media editor crop * Simplify * Simplify the tests a little * Further test tidying * Clarify comment * Add fallback to the cached attachment * Simplify, we don't need the third param Co-authored-by: andrewserong <andrewserong@git.wordpress.org> Co-authored-by: ramonjd <ramonopoly@git.wordpress.org> Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org> Co-authored-by: gregbenz <gregbenz@git.wordpress.org>

coderabbitai · 2026-09-03T11:59:55Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: e5fd1bd8-59f2-4e29-ba3d-6756b55c20e5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

* Initial fix for gallery images with links no longer being `object-fit: cover` * Limit fix to flex galleries, avoid applying to grid gallery * Changelog * Fix dynamic gallery case * PR feedback --------- Co-authored-by: talldan <talldanwp@git.wordpress.org> Co-authored-by: andrewserong <andrewserong@git.wordpress.org> Co-authored-by: ramonjd <ramonopoly@git.wordpress.org> Co-authored-by: SainathPoojary <sainathpoojary@git.wordpress.org> Co-authored-by: Azragh <azragh@git.wordpress.org>

…andalone pages (#82254) Co-authored-by: shameemreza <shameemreza@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org> Co-authored-by: annezazu <annezazu@git.wordpress.org>

github-actions · 2026-09-03T13:14:20Z

Size Change: +1.08 kB (+0.01%)

Total Size: 7.75 MB

📦 View Changed

Filename	Size	Change
`build/modules/vips/worker.min.js`	3.69 MB	+102 B (0%)
`build/scripts/block-editor/index.min.js`	428 kB	+80 B (+0.02%)
`build/scripts/block-library/index.min.js`	355 kB	+409 B (+0.12%)
`build/scripts/edit-post/index.min.js`	52.9 kB	+28 B (+0.05%)
`build/scripts/editor/index.min.js`	502 kB	+188 B (+0.04%)
`build/scripts/media-utils/index.min.js`	121 kB	+4 B (0%)
`build/scripts/upload-media/index.min.js`	16.4 kB	+59 B (+0.36%)
`build/styles/block-library/accordion-panel/style-rtl.css`	118 B	+41 B (+53.25%)	🆘
`build/styles/block-library/accordion-panel/style-rtl.min.css`	110 B	+40 B (+57.14%)	🆘
`build/styles/block-library/accordion-panel/style.css`	118 B	+41 B (+53.25%)	🆘
`build/styles/block-library/accordion-panel/style.min.css`	110 B	+40 B (+57.14%)	🆘
`build/styles/block-library/style-rtl.css`	22.4 kB	+14 B (+0.06%)
`build/styles/block-library/style-rtl.min.css`	18.9 kB	+11 B (+0.06%)
`build/styles/block-library/style.css`	22.6 kB	+15 B (+0.07%)
`build/styles/block-library/style.min.css`	18.9 kB	+11 B (+0.06%)

_{compressed-size-action}

github-actions · 2026-09-04T09:20:08Z

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: t-hamano <wildworks@git.wordpress.org>
Co-authored-by: hbhalodia <hbhalodia@git.wordpress.org>
Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org>
Co-authored-by: ellatrix <ellatrix@git.wordpress.org>
Co-authored-by: wprashed <wprashed@git.wordpress.org>
Co-authored-by: shail-mehta <shailu25@git.wordpress.org>
Co-authored-by: andrewserong <andrewserong@git.wordpress.org>
Co-authored-by: talldan <talldanwp@git.wordpress.org>
Co-authored-by: shameemreza <shameemreza@git.wordpress.org>
Co-authored-by: antwonw <antwonw@git.wordpress.org>
Co-authored-by: ntsekouras <ntsekouras@git.wordpress.org>
Co-authored-by: mukeshpanchal27 <mukesh27@git.wordpress.org>
Co-authored-by: Jiwoon-Kim <kimjiwoon@git.wordpress.org>
Co-authored-by: draganescu <andraganescu@git.wordpress.org>
Co-authored-by: ramonjd <ramonopoly@git.wordpress.org>
Co-authored-by: manzoorwanijk <manzoorwanijk@git.wordpress.org>

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

adamsilverstein · 2026-09-04T15:50:53Z

I merged this pr and am going to cherry pick it back to the cherry-pick-wp-7.1.1 branch

Media Utils: Preserve arrays in multipart form data #82353

Co-authored-by: antwonw <antwonw@git.wordpress.org> Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org> Co-authored-by: t-hamano <wildworks@git.wordpress.org>

t-hamano · 2026-09-05T06:18:41Z

Regarding the CI error, it should be resolved by cherry-picking #82478.

draganescu · 2026-09-08T18:23:33Z

Apparently I need to cherry pick a2e9438 to get the tests to pass.

* CI: Add a shared action for a single PR automation comment Every automation posts its own comment today, so a pull request collects three to five bot comments before a human says anything. Add tools/pr-meta, an action that maintains one comment split into marker-delimited sections. Each producer owns one section and rewrites only its own, so the comment reads the same however the workflows interleave. Writers hold a shared concurrency group rather than verifying their own write, which cannot detect a lost update: two writers reading the same body both succeed, and the first section is gone. queue: max is required there, since the default cancels a pending writer once a third arrives. actionlint does not know the queue key. Its last release predates the feature and rhysd/actionlint#654 is open, so suppress that one message. The action imports nothing: depending on @actions/core would mean a full npm install in every writer job just to edit a comment. * CI: Report the bundle size in the shared PR comment compressed-size-action sets its rendered markdown as an output before it decides whether to comment, so use-check diverts the comment into a check run and the body still reaches the shared comment. use-check is conditional on the pull request not being from a fork. A fork's token cannot create a check, and unlike its comment path, its check path does not catch that failure and would fail the job. * Report Flaky Tests: Render the report instead of commenting The action now writes markdown to output-path and no longer talks to GitHub, so the report joins the shared PR comment. Its repo-token input and its GitHub API client go with it. The workflow only invoked the action when a report artifact existed, so a clean run could never clear a stale report. The writer job now runs on every pull request and treats the missing artifact as an empty section. * CI: Post the performance results on the pull request The results were only ever written to the job summary, buried in the logs of a workflow run. Limiting the number of bot comments was the stated reason for not posting them, which the shared comment removes. Each shard already renders a summary, so upload those and merge them in the results job, keeping the heading and preamble they share once. * CI: Check the type label in the workflow itself github-action-required-labels cannot report through the shared comment: its failure path exposes only a status, never the rendered message or the labels it matched. Turning its comment off also disables the branch that deletes its own warning once the labels are fixed, which would strand a warning on every pull request that ever had one. The rule is one label matching ^\[Type\], so read the labels directly. Read them at the point of writing rather than from the event payload, since runs queue behind each other and an older one can arrive after a newer one already fixed them. Also fire on opened and reopened. A pull request opened without a type label got no warning until some unrelated event happened. * Project Automation: Expose the contributor prompts as outputs Both first-time contributor tasks posted their own comment: a welcome on the pull request, and a prompt to link a WordPress.org profile once it merged. They now set outputs and the workflow posts them, so both join the shared PR comment. The account link task runs on push, whose payload carries no pull request number, so it exposes the one it resolved alongside the prompt. Its writer needs that for the comment and for the concurrency group both. * Changelogs: Reference the pull request * PR meta: Add publishConfig and emoji section headings Every other tools/* workspace carries publishConfig despite being private, and the repo-wide lint rule requires it. Lead each heading with an emoji so a reader can pick their section out of a comment holding seven of them without reading any of the others. * PR meta: Wrap the comment title in emoji Marks the comment as automation at a glance, matching the section headings below it. * PR meta: Collapse the long sections behind a fold Performance tables and flaky test traces would otherwise push the rest of the comment out of view. The fold sits outside the section delimiters, alongside the heading and the footer. Everything between them is read back as the body, so a fold kept inside would nest into itself on every write. * PR meta: Do not let a failed check clear a section Three ways a section was cleared by something other than a result: Every write re-renders every section, footers included, so a writer for a PR-state section needs the head too. Without it, updating Labels dropped the 'not the current head' marker from a stale Bundle size, presenting an old result as current. The label reporter ran even when the check step failed, where a missing body file means 'labels are fine', so a failed API call erased a warning nothing had disproved. The flaky renderer treated every readdir failure as a clean run. Only a missing directory means clean; anything else now surfaces. * PR meta: Skip the write when the head cannot be read Swallowing that failure re-rendered every section without a head, which strips the 'not the current head' footer from stale results and presents them as current. Letting it reach the outer handler skips the write instead, and adds the first tests covering the action's entry point. Also drop the two dependencies report-flaky-tests no longer uses, consolidate its unreleased changelog entries now that it renders rather than comments, and document the automation action's new outputs. * PR meta: Truncate between blocks, and fail a broken flaky run Truncation cut at a fixed offset, so a cut landing inside a stack trace left the fence open and rendered the note and its link as code. It now cuts at a paragraph break and closes whatever fences and disclosures the cut left open. The flaky renderer logged its errors and left the step green, which looks exactly like a clean run, so the writer downstream cleared a report that nothing had disproved. It now fails the step, and the writer runs only when the job producing the report succeeded. Also update the README, package description and action description, which still described the action as posting a comment. Co-authored-by: manzoorwanijk <manzoorwanijk@git.wordpress.org> Co-authored-by: ciampo <mciampini@git.wordpress.org> (cherry picked from commit a2e9438) Adapted for wp/7.1: - The performance.yml changes are not ported: they build on the sharded performance workflow that only exists on trunk. - The bundle-size.yml and end2end-test.yml changes are applied onto the branch's older job layout (no .github/setup-npm, branch-pinned action hashes); end2end folds the render step into merge-artifacts as on trunk and drops the trunk-checkout report-to-issues job. - report-flaky-tests keeps @playwright/test at ^1.61.1 so the branch's Playwright version stays pinned. - Trunk-only drift entries are dropped from the project-management-automation changelog. - packages/report-flaky-tests/src/types.ts comes along from trunk: the rewritten sources use ReportedFlakyTest, which trunk added earlier. - tools/pr-meta and report-flaky-tests extend the branch's tsconfig.base.json, as the dev/build tsconfig split does not exist on wp/7.1. - An obsolete snapshot left by the replaced test suite is pruned. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DP49q1JdSxUhzFFE7ga2DS

The wp/7.1 adaptation of the unified PR comment tooling (#82249) brought trunk's jest 30 ranges into report-flaky-tests and tools/pr-meta, while every other workspace on this branch pins the 29 line. syncpack enforces one version per dependency across the repo, so lint:deps failed. Align @jest/test-result and jest-message-util to ^29.6.2 and @types/jest to ^29.5.14, matching the rest of the branch. Typecheck, lint and the 47 unit tests of both workspaces pass unchanged on jest 29. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DP49q1JdSxUhzFFE7ga2DS

github-actions · 2026-09-08T19:19:00Z

🤖 PR meta 🤖

📦 Bundle size

Size Change: +1.29 kB (+0.02%)

Total Size: 7.75 MB

📦 View Changed

Filename	Size	Change
`build/modules/vips/worker.min.js`	3.69 MB	+102 B (0%)
`build/scripts/block-editor/index.min.js`	428 kB	+80 B (+0.02%)
`build/scripts/block-library/index.min.js`	355 kB	+409 B (+0.12%)
`build/scripts/edit-post/index.min.js`	52.9 kB	+28 B (+0.05%)
`build/scripts/editor/index.min.js`	502 kB	+276 B (+0.06%)
`build/scripts/media-utils/index.min.js`	121 kB	+4 B (0%)
`build/scripts/upload-media/index.min.js`	16.5 kB	+179 B (+1.1%)
`build/styles/block-library/accordion-panel/style-rtl.css`	118 B	+41 B (+53.25%)	🆘
`build/styles/block-library/accordion-panel/style-rtl.min.css`	110 B	+40 B (+57.14%)	🆘
`build/styles/block-library/accordion-panel/style.css`	118 B	+41 B (+53.25%)	🆘
`build/styles/block-library/accordion-panel/style.min.css`	110 B	+40 B (+57.14%)	🆘
`build/styles/block-library/style-rtl.css`	22.4 kB	+14 B (+0.06%)
`build/styles/block-library/style-rtl.min.css`	18.9 kB	+11 B (+0.06%)
`build/styles/block-library/style.css`	22.6 kB	+15 B (+0.07%)
`build/styles/block-library/style.min.css`	18.9 kB	+11 B (+0.06%)

_{3f82d42 Run}

🏁 Flaky tests

Show the failures

Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

Should save the changes in /test/e2e/specs/editor/plugins/wp-editor-meta-box.spec.js, passed after 2 failed attempts.

TimeoutError: page.waitForFunction: Timeout 10000ms exceeded.
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/plugins/wp-editor-meta-box.spec.js:37:14
TimeoutError: locator.click: Timeout 10000ms exceeded.
Call log:
  - waiting for locator('role=button[name="Visual"i]')

    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/plugins/wp-editor-meta-box.spec.js:36:55

should update the HTML only for the latest navigation in /test/e2e/specs/interactivity/router-navigate.spec.ts, passed after 1 failed attempt.

TypeError: resolveLink2 is not a function
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:100:39
    at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:100:3

_{3f82d42 Run}

(cherry picked from commit a474f40)

The report-flaky-tests action runs its TypeScript sources directly under Node 24, which resolves relative imports only with an explicit extension. Trunk made this change in #81218, but the branch picked up the Node 24 action config from #82249 without it, so the "Render the flaky tests report" step crashes with ERR_MODULE_NOT_FOUND whenever a test flaked. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JrQHYVWEr61osMiYVd4AJG

manzoorwanijk · 2026-09-09T07:07:15Z

⚠️ Heads up: #82635 has been merged into wp/7.1 branch. We may want to update this PR.

t-hamano · 2026-09-09T12:09:57Z

For minor releases, the key is to cherry-pick all necessary PRs as-is and to resolve any resulting conflicts appropriately. While the backport-changelog and lib directories are indeed incorporated into the wp/7.1 branch, this is purely for convenience. These directories are not actually merged into the core.

t-hamano

Looks good from my end.

The following PRs have not been merged yet, and therefore not cherry-picked:

#82265 @adamsilverstein

Since this seems to have already been approved, we could cherry-pick this as well, but I'll leave the decision to everyone.

adamsilverstein · 2026-09-09T16:04:03Z

Looks good from my end.

The following PRs have not been merged yet, and therefore not cherry-picked:

Media: Only blame the browser's codecs when HEIC really cannot be decoded #82265 @adamsilverstein

Since this seems to have already been approved, we could cherry-pick this as well, but I'll leave the decision to everyone.

Yes, I am fixing the CI now and then will merge and cherry pick

adamsilverstein · 2026-09-09T16:38:34Z

I committed https://core.trac.wordpress.org/ticket/66056 and reopened for backport consideration. i'll need a second committer sign off. Thats the backport for #81947 PHP.

…oded (#82265) Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org> Co-authored-by: andrewserong <andrewserong@git.wordpress.org> (cherry picked from commit 2b05028)

adamsilverstein · 2026-09-09T16:42:10Z

I cherry picked

Media: Only blame the browser's codecs when HEIC really cannot be decoded #82265 in 3f82d42

adamsilverstein · 2026-09-09T23:54:12Z

WordPress/wordpress-develop#13412 has been cherry picked back to the 7.1 branch in https://core.trac.wordpress.org/changeset/63572

Re-pin to the current head of the WordPress/gutenberg#82383 cherry-pick branch, which adds the #81947, #82265, and #82249 backports on top of the previous pin. Only the `editor` and `upload-media` package hashes change in the regenerated manifest. See #66037. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WRsjgMZe3xuN98DYxZ3Kf6

Re-pins to the `wp/7.1` tip now that the 7.1.1 cherry-pick PR (WordPress/gutenberg#82383) has landed via rebase and merge. The build content is identical to the previous pin `3f82d42`, so the regenerated manifests are unchanged and only the pinned hash differs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GXuW8W41AXnGkpT3hfEhzE

t-hamano and others added 9 commits September 3, 2026 14:47

Block Editor: Add translator context to pseudo-state labels (#81770)

17bb147

Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: tellthemachines <isabel_brison@git.wordpress.org>

Fix: Post Editor: 403 on /wp/v2/settings at boot for users without ma…

6f8ab01

…nage_options cap (#81813) * Resolve the preloading correctly based on the capabilities * Remove read cap check and fetch global style for non-admin using view context

Media: Refuse a multi-file drop on a placeholder that takes one file (#…

5e4257c

…82046) Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org> Co-authored-by: andrewserong <andrewserong@git.wordpress.org>

List: outdent an empty middle item without adding an item (#82011)

7a056e1

github-actions Bot added [Package] Editor /packages/editor [Package] Block library /packages/block-library [Package] Block editor /packages/block-editor [Package] Edit Post /packages/edit-post [Package] wp-build /packages/wp-build labels Sep 3, 2026

draganescu added the [Type] Task Issues or PRs that have been broken down into an individual action to take label Sep 3, 2026

talldan and others added 2 commits September 3, 2026 15:53

Pages: require authentication and a capability to render generated st…

0cdc115

…andalone pages (#82254) Co-authored-by: shameemreza <shameemreza@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org> Co-authored-by: annezazu <annezazu@git.wordpress.org>

draganescu force-pushed the cherry-pick-wp-7.1.1 branch from fd4b429 to 0cdc115 Compare September 3, 2026 13:06

draganescu self-assigned this Sep 3, 2026

draganescu marked this pull request as ready for review September 4, 2026 09:19

Media Utils: Preserve arrays in multipart form data (#82353)

8d7fcc4

Co-authored-by: antwonw <antwonw@git.wordpress.org> Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org> Co-authored-by: t-hamano <wildworks@git.wordpress.org>

github-actions Bot added [Package] E2E Tests /packages/e2e-tests [Package] Media Utils /packages/media-utils labels Sep 4, 2026

This was referenced Sep 5, 2026

Query Loop: Fall back to post when the query has no postType #82465

Merged

Image block cropping: Sync image size and link destination settings #82316

Merged

This comment was marked as off-topic.

Sign in to view

draganescu closed this Sep 7, 2026

draganescu reopened this Sep 7, 2026

draganescu mentioned this pull request Sep 7, 2026

General: Bump the pinned hash for Gutenberg to dd294ab (7.1.1 package update) WordPress/wordpress-develop#13422

Closed

github-actions Bot added the [Package] Project management automation /packages/project-management-automation label Sep 8, 2026

adamsilverstein and others added 2 commits September 8, 2026 17:41

Editor: Store the finalize response as the attachment record (#81947)

e2a9c8d

(cherry picked from commit a474f40)

manzoorwanijk mentioned this pull request Sep 9, 2026

WP 7.1: Update Node.js to v24 LTS and npm to v11 (#82370) #82635

Merged

Merge branch 'wp/7.1' into cherry-pick-wp-7.1.1

d62073f

mukeshpanchal27 reviewed Sep 9, 2026

View reviewed changes

Comment thread backport-changelog/7.2/13051.md

draganescu mentioned this pull request Sep 9, 2026

Backport changelog: file the states.php entry under 7.1 #82674

Closed

draganescu force-pushed the cherry-pick-wp-7.1.1 branch from de457f2 to d62073f Compare September 9, 2026 12:09

t-hamano approved these changes Sep 9, 2026

View reviewed changes

Media: Only blame the browser's codecs when HEIC really cannot be dec…

3f82d42

…oded (#82265) Co-authored-by: adamsilverstein <adamsilverstein@git.wordpress.org> Co-authored-by: andrewserong <andrewserong@git.wordpress.org> (cherry picked from commit 2b05028)

draganescu merged commit dd294ab into wp/7.1 Sep 10, 2026
56 of 57 checks passed

draganescu deleted the cherry-pick-wp-7.1.1 branch September 10, 2026 08:28

aduth mentioned this pull request Sep 16, 2026

Fix Debian bullseye in wp-env for wp/6.9 #83042

Draft

github-actions Bot mentioned this pull request Sep 17, 2026

Update WordPress core from 6.9.4 to 7.1.1 MatthiasReinholz/wp-core-base#97

Open

Conversation

draganescu commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PHP changes needing Core patches

How to test

Uh oh!

coderabbitai Bot commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

github-actions Bot commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Sep 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

adamsilverstein commented Sep 4, 2026

Uh oh!

t-hamano commented Sep 5, 2026

Uh oh!

This comment was marked as off-topic.

draganescu commented Sep 8, 2026

Uh oh!

github-actions Bot commented Sep 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🤖 PR meta 🤖

📦 Bundle size

🏁 Flaky tests

Uh oh!

manzoorwanijk commented Sep 9, 2026

Uh oh!

Uh oh!

t-hamano commented Sep 9, 2026

Uh oh!

t-hamano left a comment

Choose a reason for hiding this comment

Uh oh!

adamsilverstein commented Sep 9, 2026

Uh oh!

adamsilverstein commented Sep 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

adamsilverstein commented Sep 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

adamsilverstein commented Sep 9, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

16 participants

draganescu commented Sep 3, 2026 •

edited

Loading

coderabbitai Bot commented Sep 3, 2026 •

edited

Loading

github-actions Bot commented Sep 3, 2026 •

edited

Loading

github-actions Bot commented Sep 4, 2026 •

edited

Loading

github-actions Bot commented Sep 8, 2026 •

edited

Loading

adamsilverstein commented Sep 9, 2026 •

edited

Loading

adamsilverstein commented Sep 9, 2026 •

edited

Loading