This issue is for tracking changes for the 0.1.1 release. Target release date: 1 December 2025.

Pre-release steps

• Review and merge Feat: wp playground integration #85.

Release steps

• Branch: Starting from develop, cut a release branch named release/0.1.1 for your changes.
• Version bump: Bump the version number in ai.php, package-lock.json (twice), package.json, and readme.txt if it does not already reflect the version being released. In includes/bootstrap.php, ensure you're updating the AI_EXPERIMENTS_VERSION version constant.
• Update @since: Find all new @since x.x.x lines and update those with the new version number in place of x.x.x.
• Changelog: Add/update the changelog in CHANGELOG.md and in readme.txt.
• Props: update CREDITS.md file with any new contributors, confirm maintainers are accurate.
• Readme updates: Make any other readme changes as necessary in README.md and readme.txt.
• Roadmap updates: Update ROADMAP.md based on what's in/out of this release and planned for upcoming releases.
• New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .gitattributes.
• Merge: Make a non-fast-forward merge from your release branch to develop (or merge the pull request), then do the same for develop into trunk (git checkout trunk && git merge --no-ff develop). trunk now contains the stable development version.
• Push: Push your trunk branch to GitHub (e.g. git push origin trunk).
• Wait for build: Head to the Actions tab in the repo and wait for it to finish if it hasn't already. If it doesn't succeed, figure out why and start over.
• Check the build: Check out the trunk branch and test for functionality locally.
• Test: Check the end-to-end tests are passing. Only proceed if everything tests successfully.
• Release: Create a new release, naming the tag and the release with the new version number, and targeting the trunk branch. Paste the changelog for the release from CHANGELOG.md into the body of the release and include a link to [View all items closed in the milestone](https://github.com/wordpress/ai/milestone/5?closed=1). The release should now appear under releases.

Post-release steps

• Close milestone: Edit the milestone with release date (in the Due date (optional) field) and link to GitHub release (in the Description field), then close the milestone.
• Punt incomplete items: If any open issues or PRs which were milestoned for 0.1.1 do not make it into the release, update their milestone to 0.2.0 or Future Release.
• Announce: Publish release announcement post on Make/AI, cross-posting to Make/Core and Make/Test (example).
• Profile badges: Grant new contributors the Core AI Contributor profile badge.