graphprotocol / graphprotocol/graph-node
[Bug] #4507 introduced an undocumented breaking change
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Bug report
👋 Hello! #4507 introduced a breaking change as noted here: https://github.com/graphprotocol/graph-node/pull/4507#issuecomment-1587769813
However the release notes do not include information on this breaking change: https://github.com/graphprotocol/graph-node/releases/tag/v0.32.0
Just wanted to open this to request it be added so others don't experience any outage, thank you!
Relevant log output
No response
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
- Tick this box if this bug is caused by a regression found in the latest release.
- Tick this box if this bug is specific to the hosted service.
- I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
None
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
Review the breaking-change details in the linked pull request comment and compare them with the v0.32.0 release notes. Update the release notes so the change and its impact are documented clearly, with completion confirmed when users can identify the breaking behavior before upgrading.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100