Repository navigation
docs: document the SDK release/publish process - #756
Merged
Merged
Conversation
cdecker
enabled auto-merge (rebase)
October 14, 2026 13:28
Captures how each artifact is published (crates.io via semver tags, npm via push-to-main, python built-not-published, clnvm manual twine), tag/Version-Match conventions, dependency-order publishing, the license/repository manifest requirement, the secrets inventory and rotation cadence, and the known gaps (rebase-merge npm skip, PyPI not wired, swift in a separate repo).
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
1 participant
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.
Adds
reference/releases.md("Releasing the Greenlight SDK") and a nav entry. Documents how each artifact is published, tag/version conventions, dependency-order publishing, manifest metadata requirements, the secrets inventory + rotation cadence, and the known gaps/gotchas.