Skip to content

Defensive hardening improvements for 6.9.3 - #528

Merged
priethor merged 9 commits into
trunkfrom
priethor/harden-field-data-handling
Jul 29, 2026
Merged

Defensive hardening improvements for 6.9.3#528
priethor merged 9 commits into
trunkfrom
priethor/harden-field-data-handling

Conversation

@priethor

@priethor priethor commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

This PR brings trunk in sync with the defensive hardening improvements released in SCF 6.9.3.

  • Harden REST field value formatting
  • Harden block template resolution
  • Harden relational field query results
  • Harden Options Page save scoping
  • Harden multisite Local JSON write scoping
  • Sync the 6.9.3 changelog, generated documentation, and version metadata

Use of AI Tools

Codex and Claude were used to implement these changes, guided and reviewed by @ockham and me.

@github-actions

Copy link
Copy Markdown

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.

Core Committers: Use this line as a base for the props when committing in SVN:

Props priethor, bernhard-reiter.

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

@priethor priethor added this to the 6.9.3 milestone Jul 29, 2026
@priethor

Copy link
Copy Markdown
Contributor Author

The failing e2e tests are also occurring in trunk due to an unrelated WordPress trunk change; I'll merge this with only those tests failing and follow up with a patch to fix them.

@priethor
priethor merged commit b520d2c into trunk Jul 29, 2026
30 of 35 checks passed
@priethor
priethor deleted the priethor/harden-field-data-handling branch July 29, 2026 09:57
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.

2 participants