GraphQL Code Generator Releases Changelog

Uniform Changelog API

Access The Guild changelog updates through our uniform API. Same JSON structure across all sources — no adapter-specific parsing needed.

API Endpoint

GET https://watchchangelog.com/api/v1/entries?source=graphql-codegen.releases

Response Sample

{
  "source": "graphql-codegen.releases",
  "vendor": "The Guild",
  "id": "tag:github.com,2008:Repository/75657790/release-1787495316234",
  "published_at": "2026-08-23T14:28:36.000Z",
  "title": "August 23, 2026",
  "url": "https://github.com/dotansimha/graphql-code-generator/releases/tag/release-1787495316234",
  "summary": "@graphql-codegen/cli@7.3.1 Patch Changes #10924 0c8f5ba Thanks @eddeee888 ! - Fix profiler output not being written to the filesystem in watch mode ( --profile --watch ) The profiler trace was only written on the non-watch code path, after the watch-mode early return, so a profiled watch session never produced a codegen-*.json file. The profiler now writes a fresh trace file after the initial run and after every rebuild, with each file containing only that run's events. A failed rebuild does not produce a trace and its events are discarded so they don't leak into the next successful run. The Profiler now owns its own trace lifecycle: a new clear() method starts a new trace a new outputName property provides the filename for the current trace ( null for the noop profiler) filename generation was removed from CodegenContext Updated dependencies [ 0c8f5ba ]: @graphql-codegen/plugin-helpers@7.2.1 @graphql-codegen/plugin-helpers@7.2.1 Patch Changes #10924 0c8f5ba Thanks @eddeee888 ! - Fix profiler output not being written to the filesystem in watch mode ( --profile --watch ) The profiler trace was only written on the non-watch code path, after the watch-mode early return, so a profiled watch session never produced a codegen-*.json file. The profiler now writes a fresh trace file after the initial run and after every rebuild, with each file containing only that run's events. A failed rebuild does not produce a trace and its events are discarded so they don't leak into the next successful run. The Profiler now owns its own trace lifecycle: a new clear() method starts a new trace a new outputName property provides the filename for the current trace ( null for the noop profiler) filename generation was removed from CodegenContext",
  "tags": [
    "The Guild",
    "graphql-codegen.releases",
    "graphql",
    "codegen",
    "tooling"
  ]
}