Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: graphprotocol/graph-node
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.36.0
Choose a base ref
...
head repository: graphprotocol/graph-node
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.36.1
Choose a head ref
  • 6 commits
  • 14 files changed
  • 5 contributors

Commits on Dec 4, 2024

  1. compiler fix

    @zorancv
    Zoran Cvetkov authored and zorancv committed Dec 4, 2024
    Configuration menu
    Copy the full SHA
    a8b590f View commit details
    Browse the repository at this point in the history

Commits on Dec 18, 2024

  1. Bump version number, add release notes (#5718)

    @encalypto
    encalypto authored Dec 18, 2024
    Configuration menu
    Copy the full SHA
    1d29605 View commit details
    Browse the repository at this point in the history

Commits on Jan 8, 2025

  1. ipfs: improve ipfs client selection (#5723)

    @isum
    isum authored Jan 8, 2025
    Configuration menu
    Copy the full SHA
    453bcea View commit details
    Browse the repository at this point in the history

Commits on Jan 9, 2025

  1. node: fix description not displaying for graphman deploy

    @shiyasmohd
    shiyasmohd committed Jan 9, 2025
    Configuration menu
    Copy the full SHA
    40d2f0a View commit details
    Browse the repository at this point in the history

  2. runtime: add log message on critical logs

    @shiyasmohd
    shiyasmohd committed Jan 9, 2025
    Configuration menu
    Copy the full SHA
    a5d30ce View commit details
    Browse the repository at this point in the history

  3. store: Fix handling of enum arrays 

    Roundtripping arrays of enums would fail because we would read an array of
enums back as a single string "{yellow,red,BLUE}" instead of the array
["yellow", "red", "BLUE"]. Storing an update to such an entity, even if
users make no changes to that field, would fail because Postgres expects an
array and we were sending a scalar value.

This fixes a bug introduced in PR
#5372
    @lutter
    lutter committed Jan 9, 2025
    Configuration menu
    Copy the full SHA
    fea46ab View commit details
    Browse the repository at this point in the history
Loading