Skip to content

release: prepare 0.2.25 - #162

Merged
lidge-jun merged 1 commit into
mainfrom
dev
Sep 11, 2026
Merged

lidge-jun merged 1 commit into
mainfrom
dev

Conversation

@lidge-jun

Copy link
Copy Markdown
Owner

Release preparation for 0.2.25, following docs-site/src/content/docs/development/release.md.

What this carries

Everything already promoted in #161 — the Windows issue sweep (#109, #131, #132, #133, #134) and the memory/recall sweep (#135#144) — plus the version surfaces that #161 did not touch.

Version surfaces

check-versions.mjs 0.2.25 reports OK — every surface declares 0.2.25:

  • package.json, package-lock.json
  • plugins/codexclaw/.codex-plugin/plugin.json0.2.25+codex.20260911171412
  • the nine component packages
  • cli and plugins/codexclaw/gui (bumped in every prior release commit, though check-versions does not enumerate them)
  • inventory.plugin.packageVersion and inventory.plugin.manifestVersion

The inventory was regenerated with inventory.mjs --write --tests 3133. Per the release doc the count comes from the tests line of a real run, not pass: the local suite reports tests 3133, and pass is environment-dependent.

Evidence on the exact commit

dff95d19 is green on all three lanes the release gate reads by SHA:

workflow conclusion
CI success
WSL success
Packed install lifecycle success

Next step after this merges: run the Release workflow against main with version=0.2.25 and expected_sha set to the merge commit.

Bumps every surface check-versions.mjs enumerates - package.json, the plugin manifest, the nine component packages, the cli and gui workspaces, the lockfile, and the two inventory fields - and regenerates the inventory at the measured total of 3,133 tests. The release carries the Windows issue sweep (#109, #131, #132, #133, #134) and the memory/recall sweep (#135 through #144).
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 11, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-11T17:32:42.831037Z dff95d1 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@github-actions github-actions Bot added the chore label Sep 11, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dff95d19d9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread package.json
{
"name": "codexclaw",
"version": "0.2.24",
"version": "0.2.25",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Cut the 0.2.25 changelog section with the version bump

When this release-preparation commit is published as 0.2.25, the package and manifest will advertise the new release while CHANGELOG.md still keeps the shipped changes under [Unreleased] and its comparison link remains v0.2.24...HEAD. This makes 0.2.25 appear undocumented and causes future Unreleased comparisons to include already-released commits; move the current entries into a dated [0.2.25] section and advance the Unreleased comparison base as part of this bump.

Useful? React with 👍 / 👎.

@lidge-jun
lidge-jun merged commit af44563 into main Sep 11, 2026
28 checks passed
@lidge-jun
lidge-jun deleted the dev branch September 11, 2026 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants