Subgraph versioning
While the subgraph is being indexed on top of exist one, the requests to previous version of subgraph will be declined.
It's nice to have kind of version system.
For example, I have deployed with version label v0.0.1 and then deployed with version label v0.0.2. We can promote one of this version as live mode. Also versions we are not using can be deleted or keep as previous version. One subgraph could have 5 versions of them as max.
Thanks a lot
Log in to comment and vote
Comments6
Eugene Aseev
Jan 8
Chainstack Subgraphs are being sunset on 1 Feb 2026:
https://docs.chainstack.com/changelog/chainstack-updates-january-5-2026
Please contact our transition partner Ormi Labs for future requests:
https://www.ormilabs.com/contact-us/
Info
Sep 3, 2025
•Merged request
•1 vote
Zero downtime
I would propose something like alchemy has, where you deploy your new version of subgraph and after it syncs, you put it to production.
This is effectively “zero downtime”, because now even with the fallback subgraph provider we have, the dApp shows empty data for some time while the new version of the Chainstack subgraph instance syncs (we only switch to a fallback provider in errors).
Apr 9, 2025
Aug 21, 2024
Aug 16, 2024
Oct 18, 2023