-
Notifications
You must be signed in to change notification settings - Fork 24
Labels
[Type] TaskIssues or PRs that have been broken down into an individual action to takeIssues or PRs that have been broken down into an individual action to take
Milestone
Description
This issue is for tracking changes for the 0.1.0 release. Target release date: 26 November 2025.
Pre-release steps
- Bump minimum WP version to 6.9 (ensuring this covers any additional concerns from Minimum version in plugin mismatch with documentation #94)
Release steps
- Branch: Starting from
trunk, cut a release branch namedrelease/0.1.0for your changes. - Version bump: Bump the version number in
ai.php,package-lock.json(twice),package.json, andreadme.txtif it does not already reflect the version being released. Inincludes/bootstrap.php, ensure you're updating theAI_VERSIONversion constant. - Update
@since: Find all new@since x.x.xlines and update those with the new version number in place ofx.x.x. - Changelog: Add/update the changelog in
CHANGELOG.mdand inreadme.txt. - Props: Update
CREDITS.mdfile with any new contributors, confirm maintainers are accurate. - Readme updates: Make any other readme changes as necessary in
README.mdandreadme.txt. - Roadmap updates: Update
ROADMAP.mdbased 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
trunk(or merge the pull request).trunkcontains the stable development version. - Check the build: Check out the
trunkbranch and test for functionality locally. - Release: Create a new release, naming the tag and the release with the new version number, and targeting the
trunkbranch. Paste the changelog fromCHANGELOG.mdinto the body of the release and include a link to the closed issues on the milestone (e.g.https://github.com/wordpress/ai/milestone/4?closed=1). - Close milestone: Edit the milestone with release date (in the
Due date (optional)field) and link to GitHub release (in theDescriptionfield), then close the milestone. - Punt incomplete items: If any open issues or PRs which were milestoned for
0.1.0do not make it into the release, update their milestone to0.2.0orFuture Release.
Post-release steps
- Submit to WPORG for review
- Branch
developfromtrunk, setdevelopas the base branch, update existing PRs to usedevelopas the base branch, update docs to ensure this branch change is noted - Document release steps in CONTRIBUTING.md
- Update hardcoded WP/PHP versions (besides in ai.php and readme.txt) to utilize shields.io badges to make those references dynamic
- Publish release announcement post on make/ai, cross-posting to make/core
Metadata
Metadata
Assignees
Labels
[Type] TaskIssues or PRs that have been broken down into an individual action to takeIssues or PRs that have been broken down into an individual action to take
Type
Projects
Status
Done