Version Packages - #496
Open
github-actions[bot] wants to merge 1 commit into
Open
Version Packages#496github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
September 22, 2026 13:58
3e37c1f to
5bb8cea
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
September 23, 2026 13:53
5bb8cea to
16760a1
Compare
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
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
@eddeee888/gcg-operation-location-migration@0.5.0
Minor Changes
@eddeee888/gcg-typescript-resolver-files@0.20.0
Minor Changes
3984d76: Bump ts-morph to ^28.0.0
7a5d3ac: Fix
fixObjectTypeResolverstreating an unresolvable mapper type as an empty mapper and injecting a stub for every fieldWhen a mapper aliases a type whose import cannot be resolved (a TypeScript error type — e.g. a generated client that has not been generated yet, or a module that is not installed on a fresh checkout),
fixObjectTypeResolvers(bothsmartandfast) previously treated the mapper as having zero fields and injected a resolver stub for every field of the schema type, silently overwriting hand-maintained resolver files with brokenPromise<void>stubs.The generator now detects the unresolved type, skips stub generation for that mapper (leaving existing resolvers untouched), and emits a warning naming the mapper so the underlying unresolved import surfaces instead. Genuinely empty mappers (e.g.
type FooMapper = {}) still generate stubs as before.