0.132.1 serves type definition of r133 by mistake?

[0b5vr]

• three version: Boundary between r132 / r133
• node version: ----
• npm (or yarn) version: ----

Problem description:

@types/three#0.132.1 .
I just noticed that the type signature of GLTFReference in GLTFLoader.d.ts has been changed to r133 's one by mistake.

You might possibly have been used dev instead of master when you publish 0.132.1 ...?

Relevant code:

GLTFLoader.d.ts @ @types/three#0.132.0:
https://unpkg.com/browse/@types/[email protected]/examples/jsm/loaders/GLTFLoader.d.ts

GLTFLoader.d.ts @ @types/three#0.132.1:
https://unpkg.com/browse/@types/[email protected]/examples/jsm/loaders/GLTFLoader.d.ts

The PR introduces the change ( three ):
mrdoob/three.js#21737

[0b5vr]

I can't find when you have changed this definition in this repository...? It might be your local change

[Methuselah96]

Yeah, unfortunately sometimes some changes sneak in through DefinitelyTyped and are merged in by DT maintainers without waiting for our review. In this case DefinitelyTyped/DefinitelyTyped#55977 was the PR that snuck through.

[joshuaellis]

I've left a comment addressing this issue. Thanks for raising it @0b5vr.

[0b5vr]

Ouchhh, I got the story. Thank you for addressing this, Close this issue once it is settled on DT side.

[joshuaellis]

They've just reverted that PR, r132.1 will still be broken, but r132.2 will work I believe.