Skip to content

Cover non-string attachment child MIME metadata#369

Merged
adamziel merged 1 commit into
trunkfrom
codex/upload-mime-type-nonstring
May 18, 2026
Merged

Cover non-string attachment child MIME metadata#369
adamziel merged 1 commit into
trunkfrom
codex/upload-mime-type-nonstring

Conversation

@adamziel
Copy link
Copy Markdown
Contributor

What it does

Adds focused media-validator coverage for generated-size and backup-size mime-type metadata values that are present but not strings.

Rationale

PR #368 taught the built-in WordPress upload validator to classify empty or non-string child MIME metadata as plugin-wp-attachment-metadata-invalid-shape. The fixture covered empty strings; this adds explicit non-string evidence so the guard cannot regress silently.

Implementation

The fixture now creates one generated child image with numeric mime-type metadata and one backup image with numeric mime-type metadata. The assertions verify both records appear in the built-in invalid-shape audit, while the built-in MIME-drift conflict count remains unchanged.

Testing instructions

git diff --check 'origin/trunk'...HEAD && git diff --check && git diff --cached --check
php -l tests/cow/media_validator.php
php tests/cow/media_validator.php

Add media validator fixtures for numeric generated-size and backup-size MIME metadata so the built-in invalid-shape guard is covered beyond empty strings.
@adamziel adamziel merged commit 8ba9b58 into trunk May 18, 2026
1 check passed
@adamziel adamziel deleted the codex/upload-mime-type-nonstring branch May 18, 2026 19:19
@adamziel adamziel mentioned this pull request May 18, 2026
adamziel added a commit that referenced this pull request May 18, 2026
## Release `v0.1.44`

Version bump and release metadata update for `v0.1.44`.

**Changelog draft:**
* Validate attachment child MIME metadata shape
([#368](#368))
* Cover non-string attachment child MIME metadata
([#369](#369))
* Cover explicit parent page ID holds
([#370](#370))
* Refresh merge reliability evidence for v0.1.43
([#371](#371))

**Full changelog:**
v0.1.43...release/v0.1.44

## Next steps

1. **Review** the changes in this pull request.
2. **Push** any additional edits to this branch (`release/v0.1.44`).
3. **Merge** this pull request to publish `v0.1.44`.

Merging will automatically build ForkPress binaries, create a GitHub
release, and update the Homebrew formula.

Co-authored-by: Codex <codex@openai.com>
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