Upcoming Release Changes - #10925
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
August 23, 2026 14:14
dabc65d to
212e637
Compare
Contributor
Author
💻 Website PreviewThe latest changes are available as preview in: https://pr-10925.graphql-code-generator.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@graphql-codegen/cli@7.3.1
Patch Changes
#10924
0c8f5baThanks @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-*.jsonfile.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
Profilernow owns its own trace lifecycle:clear()method starts a new traceoutputNameproperty provides the filename for the current trace (nullfor the noopprofiler)
CodegenContextUpdated dependencies
[
0c8f5ba]:@graphql-codegen/plugin-helpers@7.2.1
Patch Changes
#10924
0c8f5baThanks @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-*.jsonfile.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
Profilernow owns its own trace lifecycle:clear()method starts a new traceoutputNameproperty provides the filename for the current trace (nullfor the noopprofiler)
CodegenContext