Skip to content

docs: explain what a release tag decides about versions #232

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
barisakcam wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: explain what a release tag decides about versions #232

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ee6ac21
docs(deps): explain what a release tag decides about versions
barisakcam Sep 29, 2026
6a10d80
docs(deps): state that a tag versions the release, not an artifact, s…
barisakcam Oct 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs-gen/content/docs/tools/cli.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,12 @@ For example, `source: "https://github.com/owner/repo"`, `version: "1.0.0"`, and
https://github.com/owner/repo/releases/download/1.0.0/schema.graphql
```

#### Versions and Releases

A tag versions the release, and `metadata.yaml` must declare that same version for resolution to succeed. Every artifact in a release therefore carries the release's version.

A release holding one artifact gives that artifact a version of its own. A release holding several gives all of them the same version.

#### Identity File

For authenticated remote dependencies, `deps resolve` can read tokens from a dependency identity file.
Expand Down