Subgraph endpoint update required
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- graphql, typescript
- Domain
- api
Research direction
No file, test, or entry point is named in the issue. Locate the repository's references to The Graph hosted-service endpoint, then review the linked upgrade and querying guides; done means queries use the upgraded API key and Subgraph Studio URL.
Written by the indexing model from the issue text.
Description
Hey team,
We've noticed that you're referencing a subgraph deployed on The Graph's hosted service in this repository. Just a heads-up: after June 12th, hosted service subgraph endpoints will no longer be available as the offering is being deprecated.
If you are the subgraph owner or maintainer, it's time to upgrade your subgraph to the network. This ensures everything keeps running smoothly and you get access to all the latest features and improvements. Here is a quick guide with all the upgrade steps.
If you're not the subgraph owner or maintainer, check Graph Explorer to see if the subgraph development team has already upgraded to the network. If you don’t find an upgraded subgraph, a friendly nudge to the subgraph development team would be greatly appreciated—it's a quick process that benefits everyone. Here's the upgrade guide with all the necessary steps for the subgraph development team.
Once the subgraph is upgraded to the network, you can create an API key and updated query URL in Subgraph Studio then update this repository to query from the new endpoint, https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
Need more support or have more questions? Feel free to reach out to felix@edgeandnode.com. We're here to help!
Cheers,
Paka
- Dominant language
- TypeScript
- Stars
- 186
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from graphprotocol/graph-client
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
graphprotocol/graph-client#1029 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
graphprotocol/graph-client#1031 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
graphprotocol/graph-client#1001 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 50/100
graphprotocol/graph-client#991 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 28/100
graphprotocol/graph-client#957 ·
All issues in graphprotocol/graph-client
Similar issues
-
blocklist removal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MetaMask/eth-phishing-detect#296544 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pastelsky/bundlephobia#1122 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100