Repository navigation
docs(release): releases publish straight from the repository - #18
Merged
Merged
Conversation
Alex approved the 1.0.0 release on 2026-10-29 and asked that every release publish straight from the repository. The pre-launch rule (no tag or publish before 2026-11-01 without his approval) is replaced: merging the release-please pull request is the release approval. docs/DESIGN.md section 13 records the same, identically in all seven SDK repositories. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Codex review ( 💡 Code reviewReviewed commit:
Now that this line records that 1.0.0 shipped, the unchanged status in Verdict: APPROVE |
The SDK is released (1.0.0 on 2026-10-29) and merging the release pull request is the release approval, so the leftover pre-launch text is replaced: the README banners, the agent status line, the CONTRIBUTING release sections and the workflow comments no longer describe a private, unreleased repository or a reviewer gate on the publish environments (which have no required reviewers). docs/DESIGN.md section 2.1 records the completed didit-sdk PyPI transfer and the terms agreed with Agustin Saiz, identically in all seven repositories. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Codex review ( 💡 Code reviewReviewed commit: No actionable findings in commit Verdict: APPROVE |
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.
Problem
AGENTS.md,CLAUDE.mdanddocs/DESIGN.mdsection 13 still said nothing may be tagged or published before 2026-11-01 without Alex's explicit approval. Alex approved 1.0.0 on 2026-10-29 (now published) and asked that every release publish straight from the repository.Solution
docs/DESIGN.mdsection 13 records the 1.0.0 release, the publish path per registry and theworkflow_dispatchhand-off; the file stays byte-identical in all seven SDK repositories (sha19aec8cc2).Verification
shasum docs/DESIGN.mdis identical in sdk-python, sdk-node, sdk-go, sdk-java, sdk-php, sdk-ruby and sdk-dotnet.🤖 Generated with Claude Code