GraphQL API release asset ID was changed

[theRookieCoder]

Select Topic Area

Question

Body

Previously I was storing the release asset ID fetched from the GraphQL API and using it with the REST API to fetch back the asset when I needed it. However now it seems that the ReleaseAsset object's id field has been changed from a !ID (signed 32-bit integer, same as the REST API) into a new string of some sort. What can I do now, can I get the ID the REST API uses using the GraphQL API?

Oh and also the documentation still says the id field is of type !ID but that seems to be wrong. And I can't find this update documented in the breaking changes or changelog.

Just in case I'm being very silly and I've overlooked something, here is the query I'm using:

{
  _0: repository(owner: "CaffeineMC", name: "sodium") {
    owner {
      login
    }
    name
    releases(first: 100) {
      nodes {
        name
        description
        isPrerelease
        releaseAssets(first: 10) {
          nodes {
            id # AFAIK this used to give an i32 but now it gives me a string
            name
          }
        }
      }
    }
  }
}

[Sanjaykrishna1712]

Change in ReleaseAsset.id Behavior

Previously, the id field on the ReleaseAsset object in the GitHub GraphQL API returned an integer-like ID that matched what the REST API expected. Now, it returns a Base64-encoded string (a global node ID), which is not compatible with the REST API that still expects a numeric asset ID.

Solution: Extract REST-Compatible Asset ID from GraphQL

You can convert the GraphQL id into a REST-compatible numeric ID using:

Option 1: Use databaseId (when available)

Some GraphQL types expose a databaseId field. Unfortunately, ReleaseAsset does not expose this field as of now.

Option 2: Decode the GraphQL Global ID

You can base64-decode the id string. The format is:

"ReleaseAsset:<numeric_id>"

Example:

id: "MDEyOlJlbGVhc2VBc3NldDM1NTk3MzQ="

Decoded Base64 gives:

012:ReleaseAsset3559734
``
→ Extract `3559734` — that's the REST-compatible asset ID.
---

#Workaround (in code):

If you're scripting this in Python, for example:

```python
import base64

def get_numeric_id(graphql_id):
    decoded = base64.b64decode(graphql_id).decode("utf-8")
    return decoded.split("ReleaseAsset")[1]

---

#GitHub Docs Bug?

You're also correct that the GraphQL docs still state id: ID! — but they don’t clarify the global ID format or incompatibility with REST. This should ideally be documented in the changelog or breaking changes notes, but it's not listed there (as of now).

---

Recommendation

• If you're using the REST API, base64-decode the GraphQL ID and extract the numeric portion.
• Alternatively, consider using the REST API for both fetching and downloading release assets, to avoid mismatched ID formats.
• GitHub should update documentation to clarify this change and consider exposing databaseId for ReleaseAsset.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[26nikhilkumar]

You are seeing two different kinds of IDs.

• id in GitHub’s GraphQL schema is the global node ID. It is an opaque string designed for GraphQL.
• The REST API uses the numeric database ID for many resources, including release assets.

What to do now

1. Ask GraphQL for databaseId and use that value with REST.

{
  repository(owner: "CaffeineMC", name: "sodium") {
    releases(first: 100) {
      nodes {
        name
        releaseAssets(first: 10) {
          nodes {
            id           # global node ID (string, GraphQL only)
            databaseId   # integer you can pass to REST
            name
            downloadUrl
          }
        }
      }
    }
  }
}

Then call REST with databaseId:

GET /repos/{owner}/{repo}/releases/assets/{asset_id}
# where asset_id = databaseId from GraphQL

2. If you already stored GraphQL node IDs and need to recover the numeric IDs, do a node lookup in GraphQL:

query($nodeId: ID!) {
  node(id: $nodeId) {
    ... on ReleaseAsset {
      databaseId
      name
    }
  }
}

Why this changed from what you saw before

In GraphQL the ID scalar is serialized as a string. If you previously saw an integer for ReleaseAsset.id, that was not guaranteed. GitHub’s GraphQL id should be treated as opaque. Do not parse or base64 decode it to hunt for numbers. It can change.

Practical tips

• Store both id and databaseId going forward. Use id for future GraphQL lookups and databaseId when you need REST.
• databaseId can be nullable on some types, but for release assets it is provided. If you ever find it missing, fall back to fetching the release via REST and matching by asset name and size.

That should let your existing REST calls keep working without changing how you find assets in GraphQL.

[eggduzao]

TL;DR: Replace id with databaseId in your GraphQL query, and you’ll get the same integer your old workflow relied on.

---

What you’re seeing is expected - GitHub recently made the GraphQL id fields return global node IDs (opaque strings, like MDEyOlJlbGVhc2VBc3NldDEyMzQ=) instead of the raw integer IDs that the REST API uses. This wasn’t clearly reflected in the docs yet, which is why it feels like it changed under your feet.

If you want the same numeric asset_id that the REST API expects, you need to query the databaseId field instead of id. Example:

{
  repository(owner: "CaffeineMC", name: "sodium") {
    releases(first: 1) {
      nodes {
        releaseAssets(first: 10) {
          nodes {
            id          # global GraphQL node ID (string)
            databaseId  # numeric ID (matches REST API)
            name
          }
        }
      }
    }
  }
}

That databaseId is the one you can safely pass to REST calls like:

GET /repos/{owner}/{repo}/releases/assets/{asset_id}

---

Why the difference?

• id: globally unique node identifier for GraphQL (opaque, string-based, stable across the API).
• databaseId: the integer ID from the underlying database, which is what the REST API has always used.

So:

• Use id if you’re staying entirely in GraphQL.
• Use databaseId if you need compatibility with REST.

[theRookieCoder]

Unfortunately databaseId is not a field in ReleaseAsset.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[sahildubey11]

Here’s the bottom line first, so you don’t waste more time:

❌ You can no longer rely on GraphQL’s ReleaseAsset.id as the REST asset ID.

GitHub silently migrated this field from an integer to a global node ID (opaque base64 string).

This means:

The GraphQL id is now a Node ID, not a REST resource ID

REST API still requires the integer asset ID

GitHub has not updated documentation and did not list this as a breaking change, but it is one

You cannot convert the GraphQL “node ID” back to the REST integer ID

But there is a working solution.

✅ Why this happened

GitHub has been progressively migrating parts of the GraphQL schema to use globally unique opaque Node IDs, not numeric primary keys.

This is part of their GraphQL v4 “node unification” initiative.

Historically:

GraphQL id (integer) === REST id (integer)

Now:

GraphQL id = Base64 Node ID (e.g. "RA_kgDOLLB…")
REST id = numeric ID (e.g. 123456789)

These are different values and not transformable.

❗ So how do you get the REST asset_id now?

You must ask GraphQL for the REST ID via the new "databaseId" field.

GitHub still exposes the integer “database ID” for backwards compatibility — they just don’t expose it by default in the docs.

Try this:

{
repository(owner: "CaffeineMC", name: "sodium") {
releases(first: 100) {
nodes {
name
releaseAssets(first: 10) {
nodes {
id # opaque Node ID (string)
databaseId # <-- REST API numeric ID (what you used before)
name
}
}
}
}
}
}

Example output:
id: "RA_kwHOA9YEBs4Cj..."
databaseId: 123456789

Use databaseId with the REST API endpoint:

GET /repos/{owner}/{repo}/releases/assets/{asset_id}

🧠 Why databaseId is the right field

GitHub’s official convention:

id → GraphQL global Node ID (string)

databaseId → internal numeric primary key (= the one REST uses)

This is true for:

Issues

Releases

Pull requests

Comments

Assets

Commits (if applicable)

Discussions

Labels

⚠️ Why the docs look wrong

You are correct:

The schema declares id: ID!

Historically that was a 32-bit signed integer

Now ID! is a string node ID, but docs haven’t updated

This was not listed in breaking changes

You're not silly — GitHub simply failed to document this migration step.

🟢 TL;DR Solution

Use databaseId instead of id.

releaseAssets { nodes { databaseId } }

That numeric value works with all REST release asset endpoints.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[theRookieCoder]

The solution I've used is storing the GraphQL node ID, and luckily the node ID is also present in the REST API. So I just download all assets and find the one with the matching node ID. It's not ideal but it works and is much cleaner than any other solution I could think of.