What's the plan for the future of this plugin?

[gajus]

There have been no releases despite there having been active contributions.

We at @contra heavily rely on Relay and would want to have a functioning ESLint plugin.

Do you need help maintaining this package?

If you are not planning on maintaining this package, would you be open to handing over the namespace?

We are leaning towards publishing eslint-plugin-relay fork, but I wanted to discuss with the existing maintainers before taking any initiative here.

[captbaritone]

Hey @gajus thanks for the prompt. Our goal here is to ship tagged NPM releases from this repo off of the main branch, like we do with all the Relay packages to unblock folks who want to use more modern commits.

We also want to make shipping new NPM versions as easy as adding a commit with a new version. This should enable internal contributors, but also our newest external contributor @alloy to ship releases.

Unfortunately we are stuck on getting this automation working. It looks like you've seen our progress, and where I'm currently stuck here.

Any ideas/suggestions would be most welcome. This workflow works on the Relay repo, so I believe it should work here. We've tried with a number of NPM auth tokens from two accounts, and using both the new and legacy style tokens. No success.

Following up on this is on our list, but unless someone has ideas of something to try I suspect I won't get back to it until the new year. Any help would be great though!

[captbaritone]

Okay, we've managed to get publishing form CI figured out. Folks can grab the most recent versions of this plugin using the @main tag. The current (today) main branch of this repo is published here: https://www.npmjs.com/package/eslint-plugin-relay/v/0.0.0-main-f74143f31723425ccf83df61de3bb9cea20d8619

[eMerzh]

Cool to here you got something going :)

Hope this will enable new contributions and maintenance over this plugin