Repository navigation
Document pinned node types in the major release wave - #189
Merged
Merged
Conversation
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.
This PR updates how
RELEASING.mddescribes freezing the outgoing major's node types in codama. The current text mentions an@codama/spec-v1-style aliased pin, but codama never implemented one. Instead,@codama/upgradenow depends on the last published@codama/node-typesrelease of each older major, through a type-only, exactly pinned alias (codama-idl/codama#1201):This only changes documentation, so there's no changeset. It should merge after codama-idl/codama#1201 so the docs don't describe something that isn't in place yet.