WordPress.com Compatibility 1.0.1

This release fixes security issues in the bundled Writing Helper, so we recommend updating. Draft share links that have already been sent keep working.

Fixed

• Fix the sitemap URL in robots.txt on single sites, which had no domain and logged PHP warnings by @GaryJones in #60
• Import protected embeds into the table the [protected-iframe] shortcode reads from by @GaryJones in #61

Security

• Tighten access checks in the bundled Writing Helper: random keys for draft share links, Copy a Post limited to posts the user may read, and further hardening by @GaryJones in #62

WordPress.com Compatibility 1.0.0

The first versioned release. Its runtime code is the same as master before this release, including the PHP 8.2 and 8.4 fixes below; everything else is tooling, tests and documentation. Sites that pull master into a submodule or subtree will see new development files (such as tests/, .github/ and composer.json), none of which are loaded at runtime.

The plugin header now declares WordPress 6.4 and PHP 7.4 as the minimum versions. As a client mu-plugin, WordPress doesn't enforce them.

Fixed

• Resolve PHP 8.2 and 8.4 deprecation notices by @trepmal in #53
• Fix a redundant reference assignment in MediaRSS for PHP 8.2 by @mslinnea in #51

Maintenance

• Bring the plugin up to the VIP plugin standards baseline, with Composer tooling, integration tests, and CI for linting, tests and releases by @GaryJones in #54
• Apply the automatic coding standards fixes, with tests for the sitemaps by @GaryJones in #55
• Add doc comments and tidy the remaining code style issues by @GaryJones in #56
• Enforce the coding standards in CI by @GaryJones in #57

Documentation

• Restructure the README, documenting previously undocumented behaviour, and add contributor guidelines by @GaryJones in #54