Repository navigation
chore(release): prepare v1.3.0 - #333
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 11d3abdeae
ℹ️ 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".
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
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
Prepares Python session-peer 1.3.0 from the six merged feature PRs (#329, #330, #331, #332, #325, #328). The only runtime change is the version literal and regenerated standalone. Four-language release notes and guides describe delivery explanations, route presets/recipient addresses, bounded handoff watch, trusted SSH configuration, one-time pairing links and runtime-notice preferences at this version.
Publication-neutral text preserves the dated 1.2.1 availability checkpoint, existing platform/ACK/permission limits and historical release records. The published 0.3.3 compatibility skill asset and plugin/TypeScript versions are unchanged. Updated documentation tests check the 1.3.0 source version and the new translated note; no test guard is relaxed.
Validation
claude-opus-5-5; Codex CLI 0.163.0, isolated default model (actual backend identity unexposed). Both completed successfully on the same immutable input SHA-25624c86e72307653cf62e18113f94f397e61061b80f5ff210169bd45313fafda22with no confirmed blocker. Narrow document clarifications were then checked and tested; no identical-final-tree CLI re-review is claimed.gemini-3.8-flash-medium, medium/plan/sandbox, two separate bounded fresh reviews of the initial text and subsequent clarification delta. Both returned structured success. Codex verified and applied terminology/grammar corrections, while preserving the intended first-input research boundary. Prompt hashes:f143158f381e431cf3828bcbab143b1666fefe8efc8147d5610a903da0c03c2band3353ac0d47a0f8ad6d48337213327c45e6143b865eff3e2bdfc6ddc834d18bb6. Backend identity and native/platform acceptance are not inferred from those reviews.Release path
The owner has authorized preparation, normal protected merge, tagging and publication. Final main CI precedes the tag and empty draft. The preparation workflow must complete, including
attach-draft; all seven assets, hashes, provenance and authenticated attestations must match that exact commit before GitHub publication. The required humanpypienvironment review remains in place. The previously waived private PyPI login check is not recorded as verified.Local builds are rehearsal evidence, not uploaded release assets. Research #245/#247 remains in Long-term. Operational deployment and independent skill publication are separate.