graphprotocol / graphprotocol/docs
Clarify if version labels for subgraph deployments have to be unique
Open
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 85
- Forks
- 162
- Avg merge
- 6h 31m
- Merged PRs (30d)
- 4
Description
It's not mentioned if the version labels have to be unique. There are two possible behaviors:
- Deployments for particular version labels are immutable once made
- Deployments for particular version labels are NOT immutable
Edit: it looks like the correct answer is 1, version labels are immutable:
✖ Failed to deploy to Graph node https://api.studio.thegraph.com/deploy/: Version label already exists.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the linked Subgraph Studio deployment documentation and search the repository for the section on version labels. Clarify that version labels are immutable and that reusing one fails with the documented “Version label already exists” error; the linked page should state this behavior explicitly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100