Skip to content

Release version 0.1.0 #104

@jeffpaul

Description

@jeffpaul

This issue is for tracking changes for the 0.1.0 release. Target release date: 26 November 2025.

Pre-release steps

Release steps

  • Branch: Starting from trunk, cut a release branch named release/0.1.0 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_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 trunk (or merge the pull request). trunk contains the stable development version.
  • Check the build: Check out the trunk branch and test for functionality locally.
  • Release: Create a new release, naming the tag and the release with the new version number, and targeting the trunk branch. Paste the changelog from CHANGELOG.md into 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 the Description field), then close the milestone.
  • Punt incomplete items: If any open issues or PRs which were milestoned for 0.1.0 do not make it into the release, update their milestone to 0.2.0 or Future Release.

Post-release steps

  • Submit to WPORG for review
  • Branch develop from trunk, set develop as the base branch, update existing PRs to use develop as 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 take

Type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions