Should we expect they will be there until GraphQL provides all features given by current REST API?
databaseId field being deprecated from its inception, this isn’t a field that we intend to remove from the GraphQL schema until the complete deprecation of the REST API. We understand that the GraphQL API doesn’t have full parity with the REST API, so we keep the
databaseId around to make the transition easier but eventually we’d like to use globally unique
id fields as the source of truth in referencing an object in the API.
Should we expect a kind of release note or message to be prepared for the end of life of deprecation fields?
Yes, sit tight! We’re working on a better way to communicate deprecated pieces of schema, and when / if they will be removed from the schema - but rest assured,
databaseId isn’t going away any time soon.
As an aside, when building tools and integrations that use either GitHub’s REST API or GraphQL API, we advise you to persist both the
id so that you can easily reference those objects from either the REST API or GraphQL API.
We also hope to add a way to see the global (GraphQL) ID from any REST resource, but this functionality does not yet exist.