Revoking potentially impacted tokens from ESLint vulnerability

This post details the revocation of access tokens due to a malicious ESLint NPM package incident. It specifically impacts users of VSTS Package Management and those using access tokens in configuration files for package feeds. The action involves invalidating access tokens and provides instructions for regenerating tokens for NPM, NuGet, Maven, and Gradle. It also mentions the revocation of globally scoped access tokens used for general automation and advises users to create new personal access tokens if their automation is failing. Instructions for creating a VSTS support case are also provided.