Repository navigation
[ci] release - #1
Open
github-actions[bot] wants to merge 1 commit into
Open
github-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/main
branch
from
September 12, 2026 13:17
77070cb to
3a8b497
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 14, 2026 15:05
3a8b497 to
5cb9658
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
openapi-typescript@8.0.0
Major Changes
699ab08Thanks @darkbasic! - feat: generate TypeScript with raw string templates and drop the TypeScript dependencyopenapi-typescriptno longer uses the TypeScript compiler API (ts.factory,createPrinter,createSourceFile) at runtime. Generation now builds the.d.tssource with string templates, so the packagecompiler API — this fixes the
Cannot read properties of undefined (reading 'createKeywordTypeNode')crash,typescriptis no longer a peerdependency and is not resolved at all when generating,
allOfsemantics,including callable and readonly collection handling.
Output fixes include:
tsUnion()/tsIntersection()no longer emit a redundant single-memberunion, so
(string)[][]is nowstring[][]. Semantically identical.x-enum-descriptionsentry no longer leaks a bare token into theenum body (it used to produce invalid TypeScript); line breaks become spaces.
pathParamsAsTypes, a URL containing a backtick or${no longer breaksout of the generated template literal type.
item types retain their outer array dimension.
the published package includes the type dependencies needed by Redocly's
public declarations for consumers with
skipLibCheck: false.Breaking changes
openapiTS()now resolves to astring(the generated file body, without thecomment header) instead of an array of AST nodes. The body ends with a newline.
transformreturnsstring | { schema: string; questionToken: boolean }postTransformreceives and returnsstringtransformPropertyreceives and returns{ name, optional, readonly, type, comment?, indent };use the new
tsComment()helper to attach JSDoc from that hookGlobalContext.injectFooteris now aFooterDeclaration[](generated strings,plus a deferred
OperationsDeclarationfor theoperationsinterface)typescriptmust return the equivalent type text instead, e.g.
ts.factory.createTypeReferenceNode("Date")becomes"Date".typescriptisno longer required to use this package at all.
stringToAST(),tsModifiers()andQUESTION_TOKENwere removed and are replaced by string builders:
typeLiteral(),tupleType(),propertySignature(),indexSignature(),typeAlias(),interfaceDecl(),enumDecl(),INDENTandtsComment().injectoption is now emitted verbatim instead of being re-printed by theTypeScript printer.
astToString()now joins source strings and ensures a trailing newline. ASTnodes and the former printer options argument are no longer supported;
passing options throws instead of silently ignoring them.
postTransformconfigured, nonempty object-shaped$defsroots use typealiases so custom mapped types are valid. Root detection accepts surrounding
comments and inline formatting while retaining the empty-root fallback.
Minor Changes
323e9a5Thanks @drwpow! - Add ability to set flags in redocly.yamlPatch Changes
e2e830eThanks @darkbasic! - Generate required composed properties from required-onlyallOfmembers, including typed object constraints when custom transforms are configured.#2415
f55fb72Thanks @remy90! - SupportadditionalProperties: trueon string enums by generating a loose autocomplete union ((enum literals) | (string & {})), preserving editor suggestions while still accepting arbitrary string values.f1321d4Thanks @darkbasic! - FixenumValuesmaking sharedWithRequiredObjecthelper reuse depend on theorder of unrelated schemas. Preserve collision protection for injected source,
generated enums, and unprefixed root types.
f6960feThanks @darkbasic! - Pin Redocly OpenAPI core to a release that uses patched YAML and glob dependencies and avoids the vulnerable URI parser.219be04Thanks @darkbasic! - Support TypeScript 6 alongside TypeScript 5.Fix
Readable<T>andWritable<T>to preserve function signatures, including methods onDateandRegExp, while continuing to filter read-only and write-only properties. This fixes a pre-existing issue under both TypeScript versions, in the helpers package and in the helper types generated with--read-write-markers.Fix readonly-array methods and iteration to expose resolved elements, including schemas generated with
--immutable, while preserving readonly positional properties, length, and additional data properties. Keep the existing mutable-tuple projection and support recursive arrays and tuples. Excluded elements in readonly collections now follow the sameneverelement rule as mutable arrays. Callable types remain unchanged, including their parameters, return types, and attached properties.openapi-fetch@0.17.1
Patch Changes
#2605
b775891Thanks @kaigritun! - fix(openapi-fetch): handle empty error responses when Content-Length header is strippedUpdated dependencies [
219be04]:openapi-react-query@0.5.5
Patch Changes
#1950
ac9d082Thanks @freshgiammi! - Tag generated querykeys withDataTag, allowing us to infer the return type (data/error) associated with a given queryKey, making methods likequeryClient.setQueryData()type-safe.Updated dependencies [
b775891,219be04]:openapi-typescript-helpers@0.1.1
Patch Changes
219be04Thanks @darkbasic! - Support TypeScript 6 alongside TypeScript 5.Fix
Readable<T>andWritable<T>to preserve function signatures, including methods onDateandRegExp, while continuing to filter read-only and write-only properties. This fixes a pre-existing issue under both TypeScript versions, in the helpers package and in the helper types generated with--read-write-markers.Fix readonly-array methods and iteration to expose resolved elements, including schemas generated with
--immutable, while preserving readonly positional properties, length, and additional data properties. Keep the existing mutable-tuple projection and support recursive arrays and tuples. Excluded elements in readonly collections now follow the sameneverelement rule as mutable arrays. Callable types remain unchanged, including their parameters, return types, and attached properties.