Skip to content

Always get latest tag of types-registry #24608

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 4, 2018

Conversation

uniqueiniquity
Copy link
Contributor

If a bad version of the types registry were to get published, we'd like to be able to set the latest tag to a previous version so that type acquisition isn't broken for everyone.
However, currently, this will only help those who have not already updated to the new, bad version.
This PR aims to ensure users are always getting the version of types-registry tagged as latest so we can successful roll back all users, not just those who haven't updated yet.

@uniqueiniquity uniqueiniquity requested review from RyanCavanaugh, mhegazy, a user and billti June 1, 2018 22:54
@@ -523,12 +523,12 @@ namespace ts.server.typingsInstaller {

protected abstract installWorker(requestId: number, packageNames: string[], cwd: string, onRequestCompleted: RequestCompletedAction): void;
protected abstract sendResponse(response: SetTypings | InvalidateCachedTypings | BeginInstallTypes | EndInstallTypes): void;

protected latestDistTag = "latest";
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should probably be readonly, or leave as const and export

@uniqueiniquity uniqueiniquity merged commit 3446a79 into microsoft:master Jun 4, 2018
@uniqueiniquity uniqueiniquity deleted the latestTypesRegistry branch June 4, 2018 16:17
@microsoft microsoft locked and limited conversation to collaborators Aug 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants