Release prep — bump to 0.2.5 and roll up CHANGELOG#67
Merged
Conversation
Bumps `package.json` + `package-lock.json` from 0.2.1 → 0.2.5. Rolls every [Unreleased] entry — refine, clarify, depends_on/related frontmatter + list column, the constitution, the @inquirer/prompts drop, the api-mode drop, and skills install auto-detect — into a new [0.2.5] — 2026-04-30 — Ankur section, with a fresh empty [Unreleased] block above. The release header frames this as the host-agent-first cut: the SDK path and the interactive prompt layer both go away, voice and spec-quality rules move into `.draftwise/constitution.md`, and the spec lifecycle gains clarify (audit before tech) plus refine (re-ground without clobbering PM edits). Under 0.x semver the patch lane carries breaking changes; the api-mode and inquirer drops both remove paths a small subset of users could have depended on, while every other change is additive at the CLI surface. Tests (266) + lint clean on the bumped tree. After merge, ritual: `git tag -a v0.2.5 -m "v0.2.5"`, `git push origin v0.2.5`, `npm publish` (interactive — OTP + login may be needed if the npm session expired).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
package.json+package-lock.jsonfrom 0.2.1 → 0.2.5.[0.2.5] — 2026-04-30 — Ankursection, with a fresh empty[Unreleased]above..draftwise/constitution.md, and the spec lifecycle gainsclarify(audit before tech) plusrefine(re-ground without clobbering PM edits).Under 0.x semver the patch lane carries breaking changes; the api-mode + inquirer drops both remove paths a small subset of users could have depended on, while every other change is additive at the CLI surface.
Test plan
npm test— 266 tests pass on the bumped treenpm run lint— cleanpackage.json+package-lock.jsonboth at 0.2.5 (root + nested package entry)[Unreleased]is empty;[0.2.5]carries the full set of entries with date + authorgit tag -a v0.2.5 -m "v0.2.5",git push origin v0.2.5,npm publish