Repository navigation
Version Packages - #1845
Merged
Merged
Version Packages#1845
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 4, 2026 17:59
33c7138 to
2388b15
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
swagger-typescript-api@13.14.0
Minor Changes
ad7b7efThanks @TheeCoderAhmed! - AddemptyNotAsNever(--empty-not-as-never) to generateneverinstead ofanyfornot: {}andnot: true, which no value can satisfy. It is off by default, so generated output does not change unless you enable it.Patch Changes
#1839
e67c3a7Thanks @cpruijsen! - Stop treating a colon inside a path segment as an Express-style path parameter.Routes using AIP-136 custom methods, such as
/v1/items:searchor/v1/items/{itemId}:archive,generated a bogus required
stringargument for the:suffixand dropped it from the request URL.The generated method could only produce the correct path if the caller passed the literal
":search".:paramNameis now recognized only at the start of a path segment, so/users/:userIdkeeps workingwhile mid-segment colons stay part of the literal path.