Version Packages - #107
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 12, 2026 07:37
bd13634 to
5af7b7c
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 main, this PR will be updated.
Releases
prisma-class-generator@0.7.0
Minor Changes
#108
5696c4cThanks @kimjbstar! - AddmakeDtoFiles, which generatesCreate<Model>andUpdate<Model>classes alongside eachmodel class. They're compositions rather than copies —
CreateUser extends OmitType(User, [...] as const)andUpdateUser extends PartialType(CreateUser)— so a field's type, Swagger metadata andvalidators stay declared in exactly one place, and NestJS's mapped types carry all three through.
Imported from
@nestjs/swaggerwhenuseSwaggeris on,@nestjs/mapped-typesotherwise.A field leaves the
CreateDTO only when the schema itself says a client can't supply it: afunction-based
@default(...)(autoincrement(),uuid(),now(),dbgenerated(...), …),@updatedAt, or a relation field. Literal defaults like@default(0), relation foreign-keyscalars, and an
@idwithout a default all stay — nothing is inferred from field names. Off bydefault, so existing output is unchanged.
Patch Changes
5be2cb0Thanks @kimjbstar! - FixuseNonNullableAssertionsproducing TypeScript that doesn't compile. A field with a literal@default(...)was emitted asviews!: number = 0, which is TS1263 — "Declarations withinitializers cannot also have definite assignment assertions". Any model with at least one
defaulted field made the whole generated file fail to build, and
useUndefinedDefaulthit thesame thing. The assertion is now omitted whenever the field has an initializer, which is what
definite assignment already means.