[devmuhib009]

Unregisters the custom post status custom during tear_down() in Tests_Canonical.

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

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

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

Props devmuhib.

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

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.

[Copilot]

🟢 Approval recommended

There are no active review issues for the custom post-status teardown cleanup.

No open issues 🎉

What changed in this PR

Improves test isolation in Tests_Canonical by cleaning up the custom post status during teardown.

Changes:

• Adds _unregister_post_status( 'custom' ) before the parent teardown call.

File	Description
tests/​phpunit/​tests/​canonical.php	Unregisters the custom post status in tear_down().

_{Review effort: Balanced}

[huzaifaalmesbah]

Thanks @devmuhib009!

Correctly cleans up the registered 'custom' post status using _unregister_post_status() in Tests_Canonical::tear_down(), preventing post status leakage across canonical test runs. Looks good!

_{AI Review: Gemini 3.8 Flash}