Repository navigation
docs: explain what a release tag decides about versions - #232
Open
barisakcam wants to merge 2 commits into
Open
barisakcam wants to merge 2 commits into
barisakcam wants to merge 2 commits into
Conversation
The manifest reference says a dependency's version must match metadata.yaml and, separately, that the release URL is built from that version. Together those mean every artifact in one release carries the same version, which the reference never states. Say it, and say what follows: one release per artifact lets a consumer pin that artifact's own version, while several artifacts in one release leaves each one's version implicit in the release tag.
…implify the text for Versions and Releases added last commit
ahmdmhd
marked this pull request as ready for review
October 9, 2026 11:55
This branch has not been deployed
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.
The manifest reference says a dependency's version must match metadata.yaml and, separately, that the release URL is built from that version. Together those mean every artifact in one release carries the same version, which the reference never states.
Say it, and say what follows: one release per artifact lets a consumer pin that artifact's own version, while several artifacts in one release leaves each one's version implicit in the release tag.