Skip to content

chore(main): release leantoken 0.2.0 - #599

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-v0.1.29
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
release-v0.1.29

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 2, 2026 •

Copy link
Copy Markdown
Contributor

Changelog

All notable changes to this project will be documented in this file.

[0.2.0] - 2026-10-17

Benchmarks

Bug Fixes

Chores

  • test: Bound local concurrency and streamline focused runs

Documentation

Features

Refactoring

  • test: Consolidate process and frozen-report coverage
  • setup: Reuse launcher path matcher
  • mcp: Share resource protocol policy
  • mcp: Centralize legacy protocol shape
  • cursors: Remove unused legacy version paths

Testing

@github-actions
github-actions Bot requested a review from morluto as a code owner September 2, 2026 08:09
@github-actions github-actions Bot added the autorelease Automated release PR - merge to trigger a new release label Sep 2, 2026
@github-actions
github-actions Bot requested a review from N0zoM1z0 as a code owner September 2, 2026 08:09
@github-actions github-actions Bot added the autorelease Automated release PR - merge to trigger a new release label Sep 2, 2026
@github-actions
github-actions Bot force-pushed the release-v0.1.29 branch 7 times, most recently from 195ba5e to a66facf Compare September 8, 2026 02:15
@github-actions
github-actions Bot force-pushed the release-v0.1.29 branch 2 times, most recently from dca7c95 to 2cb4504 Compare October 5, 2026 09:10
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 6, 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-10-17T06:06:08.921204Z 4e4ccb2 Manual request
ℹ️ 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 force-pushed the release-v0.1.29 branch 13 times, most recently from f2f5fa3 to a7cc03d Compare October 6, 2026 16:11
@github-actions
github-actions Bot force-pushed the release-v0.1.29 branch 5 times, most recently from a66ed03 to 3d61aba Compare October 16, 2026 13:05

@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: 3d61abafd2

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread Cargo.toml Outdated
Comment thread CHANGELOG.md Outdated
@github-actions
github-actions Bot force-pushed the release-v0.1.29 branch 4 times, most recently from 84b52f3 to 54178a3 Compare October 16, 2026 17:31
Comment thread CHANGELOG.md Outdated
@github-actions
github-actions Bot force-pushed the release-v0.1.29 branch 4 times, most recently from f55634e to 4513dbe Compare October 17, 2026 03:28
@github-actions github-actions Bot changed the title chore(main): release leantoken 0.1.29 chore(main): release leantoken 0.2.0 Oct 17, 2026
@N0zoM1z0

Copy link
Copy Markdown
Collaborator

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 303a32a20d

ℹ️ 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".

@N0zoM1z0

Copy link
Copy Markdown
Collaborator

@codex review

Please review the regenerated candidate 8049d04, including the version-independent doctor fixture from #662. The generator automatically dispatched CI for this exact head; this remains a release candidate pending validation.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: 8049d04ab0

ℹ️ 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".

@N0zoM1z0

Copy link
Copy Markdown
Collaborator

Validated regenerated candidate 8049d04ab0d600d808d386ebb0844c3d39b795c2 after #661 and #662.

  • All four package identities are 0.2.0; the generated PR body exactly matches the latest changelog section, including the breaking ReadResponse.target_end_line migration.
  • The generator explicitly dispatched complete CI for this exact candidate. All 15 planned evidence jobs and Required checks passed. Downloaded receipts match the exact source, lane, runner, command, topology, schema and planner identities.
  • Actual 0.2.0 product logs show 1088 Linux, 1084 macOS and 1020 Windows tests passed with zero skips. Coverage, repeated test profiling, Rust quality, npm installation, dependencies, examples/docs and release planning also passed. Release planning ran all five real Git/git-cliff fixture tests and announced v0.2.0.
  • Codex and Greptile reviewed this exact head without new findings; prior release review threads are resolved. Post-merge main CI also passed.

The earlier candidate failure was reproduced rather than retried away: its version-hardcoded catalog fixture failed on all three platforms/coverage/profiling, and Required checks rejected its failed receipt. #662 corrects that fixture while preserving current-release catalog strictness. This PR remains open as a validated release candidate; no tag or package was published by this follow-up.

@N0zoM1z0

Copy link
Copy Markdown
Collaborator

@codex review

Regenerated candidate 4e4ccb2 includes #663. Its only differences from fully validated 8049d04 are release documentation and the generated changelog. Four 0.2.0 identities, body/changelog equality and the breaking migration were rechecked. Both automatically dispatched complete CI and the approved original PR workflow will run for this current candidate.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: 4e4ccb272a

ℹ️ 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".

@N0zoM1z0

Copy link
Copy Markdown
Collaborator

Final validation after #663 for candidate 4e4ccb272a91604c3f0abcd4edde29552c6b1c0c:

  • Complete dispatched candidate CI: all 15 planned evidence jobs and Required checks passed, including three-platform products/contracts, Rust quality, coverage, repeated profiling, dependencies, examples/docs, npm installation and release planning.
  • Approved original PR CI: all six selected evidence jobs and Required checks passed. The PR check summary now contains the actual checks and GitHub reports CLEAN.
  • Downloaded receipts were independently compared with each immutable plan. The dispatched plan/15 receipts bind to the exact candidate head; the PR plan binds to that head and its GitHub merge revision 78c0692601734e50266d6e486fcaa35b0bd287cb, with all six receipts matching. Source, lane, runner, command, topology, schema and planner identities agree.
  • Latest main CI passed; its 11/11 planned receipts bind to 5cfab83047d4dc77b1b5826016bc75edcd9b4bc4.
  • Rechecked four 0.2.0 package identities, exact changelog/PR-body equality and the breaking ReadResponse migration. Codex and Greptile reviewed this current candidate without new findings. No unresolved release review threads remain.

This remains an open, validated release candidate. No tag or package was published by this follow-up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autorelease Automated release PR - merge to trigger a new release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant