dependencies on other @types packages are specified as "*"

See https://github.com/DefinitelyTyped/DefinitelyTyped/pull/38624#issuecomment-537216366

Given some @types package P that depends on another @types package Q,
P's dependencies are implicitly published as

"dependencies": {
  "@types/q": "*"
}

Assume there is an update Q' and an update P' that depends on Q'.

Consumers of P who update to P' do not get Q' installed, because the old version of Q in the consumer's lockfile satisfies the dependency of "*". This leaves consumers of P to either manually edit their lockfile or explicitly depend on Q' in their application, both of which are not ideal solutions.

Definitely Typed should implicitly add the newest version of other DT packages to the published package.json.

Related: microsoft/types-publisher#11 microsoft/types-publisher#12 microsoft/types-publisher#360

Start with the linked pull-request comment and related issues microsoft/types-publisher#11, #12, and #360 to understand the publishing behavior. Trace how Definitely Typed dependencies become the published package.json, then verify that a package update causes its newest dependent @types package versions to be specified rather than "*".