Repository navigation
chore(release): Register planned version 0.3.0 - #17
Conversation
Pin the finalized source release accepted on master before publishing its annotated tag. Leave the tag object unreserved until publication, then require a reviewed follow-up to record its exact identity.
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. |
There was a problem hiding this comment.
🟢 Approval recommended
The single registry addition follows the release sequence and has no unresolved findings.
No open issues 🎉
What changed in this PR
Registers the finalized Spawn Manager 0.3.0 source release before publishing its annotated tag.
Changes:
- Adds
v0.3.0as planned, targetinga840f35e4c5bc5ee4724b4b045864a32067957f7, with the tag object left as-.
| File | Description |
|---|---|
.github/maintained-release-tags |
Adds the planned 0.3.0 release entry. |
Review effort: Balanced
![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: dd9c76afb5
ℹ️ 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".
Purpose
Register the finalized 0.3.0 source release after PR #16. This is the planned
registry step required before publishing an annotated release tag.
Changes
Add one planned manifest row for
v0.3.0, targeting the accepted sourcecommit
a840f35e4c5bc5ee4724b4b045864a32067957f7. The annotated tag does notexist yet, so its object remains
-. No source or policy changes are made.Verification and release order
Rootless Trixie registry tests and documentation generation pass. The author
self-review confirmed the exact source target, four-field row, unchanged
runtime and clean commit message. After this PR is reviewed and merged,
publish the annotated tag at that source target, then pin its object in a
separate reviewed follow-up.
Co-Authored-By: GPT-6.1 noreply@openai.com