-
Notifications
You must be signed in to change notification settings - Fork 889
Updated NuGet package? #1017
Comments
This is something we might consider when we update our build infrastructure (drop Travis, only use Circle & appveyor, and publish to NPM from CI). Will keep you posted. |
+1 |
Can this be run on Circle CI? We dropped Appveyor because it was way too flaky and slow. We'd accept a PR for this if it works on Circle. |
Circle runs on Linux, but does support Docker. I'll try to look into this vaguely soon; in theory it should be possible to spin up Mono and use it to run a https://discuss.circleci.com/t/net-projects/307/10 |
💀 It's time! 💀TSLint is being deprecated and no longer accepting pull requests for major new changes or features. See #4534. 😱 If you'd like to see this change implemented, you have two choices:
👋 It was a pleasure open sourcing with you! If you believe this message was posted here in error, please comment so we can re-open the issue! |
@JoshuaKGoldberg I hope this is not a major change and should be fixed. It is important to update the package on nuget once CVE-2020-7598 vulnerability (#4917) will be fixed. |
@WPMGPRoSToTeMa https://github.com/joshuakgoldberg/tslint.msbuild is a separate package that has options for using your own TSLint version. You could still use that if & when we fix any security vulnerabilities. 🚀 |
🤖 Beep boop! 👉 TSLint is deprecated 👈 (#4534) and you should switch to typescript-eslint! 🤖 🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋 |
There's a NuGet package available with just the npm
tslint
andtypescript
packages, but that's by a separate contributor (me!) who would be very willing to pass ownership to you (Palantir / the TSLint team).Would you be up for auto-uploading the latest tslint there whenever you push an update? Steps are available in this repo.
The text was updated successfully, but these errors were encountered: