chore(release): 0.1.29 - #934
github-actions[bot] wants to merge 20 commits into
Conversation
|
Release proposal updated through main commit The note sections still match the generated draft and were refreshed. These suggestions use merged titles, not a review of migration requirements. The committed notes remain authoritative. Highlights
Upgrade notesReview compatibility and document any required migration steps before releasing. |
|
Note To use Codex here, create a Codex account and connect to github. |
|
Release proposal updated through main commit The note sections still match the generated draft and were refreshed. These suggestions use merged titles, not a review of migration requirements. The committed notes remain authoritative. Highlights
Upgrade notesReview compatibility and document any required migration steps before releasing. |
|
Release proposal updated through main commit The note sections still match the generated draft and were refreshed. These suggestions use merged titles, not a review of migration requirements. The committed notes remain authoritative. Highlights
Upgrade notesReview compatibility and document any required migration steps before releasing. |
Summary
Keep a release proposal current with changes merged into main.
Changes
Update the package version and draft release notes. The version header and PR title are maintained by automation. Edit the marked note sections in
.github/release-notes.md; edited or deleted sections become human-owned. New suggestions appear in subsequent bot comments. The PR description is never regenerated.Testing
The updater does not run package tests. Check required CI and Codex review on the current head before merging. Request a final Codex review if the last review targets an older head. Record any additional checks here.
Risk and rollout
Merging this PR starts the existing CI and protected release process. Review migration details and complete the public disclosure review before merging.
Public disclosure review