Skip to content
This repository has been archived by the owner on Jun 11, 2020. It is now read-only.

Changes published from DefinitelyTyped are not marked as 'latest' #544

Open
DominikPalo opened this issue Dec 8, 2018 · 1 comment
Open

Comments

@DominikPalo
Copy link

Yesterday I made some changes in https://www.npmjs.com/package/@types/google-apps-script (DefinitelyTyped). My PR was merged and after few hours a new version of the NPM package was also published - as a version 0.0.33. But, when I try to install these types using the command npm install @types/google-apps-script, it still installs the old version 0.0.32. I have to explicitly use npm install @types/google-apps-script@0.0.33 to install the latest version. Then I found that the version 0.0.33 is not marked as 'latest'.

Shouldn't be all changes made on the master branch of DefinitelyTyped automatically published as 'latest' on NPM? Or am I wrong? Then how can I make changes in types to publish them as 'latest'? I didn't find anything regarding this issue in the DefinitelyTyped nor types-publisher documentation.

npm

@DominikPalo DominikPalo changed the title Changes published from DefinitelyTyped are not published as 'latest' Changes published from DefinitelyTyped are not marked as 'latest' Dec 8, 2018
@sandersn
Copy link
Member

sandersn commented Feb 1, 2019

I have also seen this bug, but only intermittently. I'm still trying to find out what causes it to happen.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants