Document publish-time version assignment - #64
Merged
Conversation
RomainCscn
force-pushed
the
codex/docs-changesets-publish-workflow
branch
2 times, most recently
from
August 26, 2026 14:16
b2df6d1 to
ac76782
Compare
RomainCscn
force-pushed
the
codex/docs-changesets-publish-workflow
branch
from
August 26, 2026 14:20
ac76782 to
3c32660
Compare
axelniklasson
approved these changes
Aug 26, 2026
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
2 participants
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.
A user was confused about how to assign a release version that is only known at publish time. This clarifies that
syncshould be run again with the version beforecomplete.We may later add a dedicated way for
completeto set the version, such as aset-versionoption, but are postponing that for now.