Repository navigation
chore(release): Pin published version 0.3.0 - #18
Merged
Merged
Conversation
Record the annotated object published at the reviewed source target. The release registry must now reject deletion or annotation changes, even when a replacement tag points to the same commit.
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-row update matches the verified published tag and leaves no unresolved findings.
No open issues 🎉
What changed in this PR
Completes the 0.3.0 release registry sequence begun in PR #17, without runtime changes.
Changes:
- Marks
v0.3.0as published and pins its annotated tag object. - Preserves the source target and existing release entries.
| File | Description |
|---|---|
.github/maintained-release-tags |
Pins the published v0.3.0 annotated tag. |
Review effort: Balanced
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.
Purpose
Pin the published annotated tag for Spawn Manager 0.3.0 after the reviewed
planned entry in PR #17. This completes the required registry sequence.
Changes
Change only the
v0.3.0row from planned to published and record annotatedobject
48292178553e49e4aed89a8abcdb1b924b7f2ce1. The source target remainsa840f35e4c5bc5ee4724b4b045864a32067957f7; tag contents and existing releasesare unchanged. Later deletion or annotation replacement must now fail.
Verification
Read back the remote tag reference and annotated object, fetched that exact
tag, and verified the real registry plus documentation in rootless Trixie.
The author self-review confirmed the unchanged target, exact object identity,
clean worktree and compliant commit message. No runtime changes are made.
Co-Authored-By: GPT-6.1 noreply@openai.com