Add “Outdated” tag for `linter-eslint-node` package

[savetheclocktower]

The last published version of linter-eslint-node under the AtomLinter organization has several bugs that have since been fixed. Now that AtomLinter has been archived, I don't have the ability to publish new packages under the old name even if I wanted to.

We've moved linter-eslint-node to a new pulsar-linter organization and are publishing updates there. Users can install it via

ppm install pulsar-linter/linter-eslint-node

and we wouldn't rule out publishing to the package registry again (under a new name) if we could figure out how to automate it.

[confused-Techie]

@savetheclocktower Was this package ever published to the registry? I feel like some time ago you and I looked at automated publishing, or at least I know I did for pulsar-cooperative.

We may want to wait to badge this package until it's published that way we can on the badge directly recommend an alternative package. But if that's not in your plans for some time then I can badge it anyway without an alternative listed.

[savetheclocktower]

It was not published to the registry. We'd have had to change the name, plus I don't think anyone has demonstrated how to publish to PPM from CI.

I'd be in favor of that, but I don't know where it fits on folks' priority list. Without knowing how long it'll take, I'd be reluctant to hit the snooze button on this indefinitely.

[confused-Techie]

I can't recall how well this was testing, but a while back I did flesh out some ideas on how to publish to the PPR in CI here if you'd like to take a look.