Automate publish of new versions

[piranna]

Nightly has added info for Node.js 20.3.0 two weeks ago, but latest published version in npm is of one month ago with info up to Node.js 20.2.0. I think publish of new packages should be done automatically as part of the nightly script.

Also, I think versioning of package should be the same of the highest Node.js version, or the date info was fetch (2023.6.25, for example), to make it easier to identify.

[zargold]

I am having this problem with Node@18.17

[chicoxyzzy]

Oh, I somehow missed the discussion.
I remember that we've tried to add automated publish, but something went wrong. I will try to find time to add it next week.

I also like the idea of versioning, that makes a lot of sense!

[wesleytodd]

Looks like this package is no longer seeing updates? I wonder, would you be interested in handing off this package to the Node project? I was working on a few small update to @pkgjs/nv and we have had this outstanding issue for a long time which I was looking at doing. If instead of updating this repo we merged the effort and published node-releases from either the official node release or even as a side effect of the nv tool it would make it a bit higher likelyhood to keep stable with maintainers around.

[chicoxyzzy]

@wesleytodd I would love to hand it off to the Node project!

[wesleytodd]

I will create an issue in the Package Maintenance WG (the group who runs the pkgjs org) and see if folks like this idea. If so we can probably work with the build and release folks to decide if it is a good idea to publish something like this right from them or if a nightly like the update does is better. Glad to hear you are open to it, with this many downloads getting stale node data I am not sure what the impact is, but doesn't seem great 😆 .

[piranna]

Good to see there's movement, tell me if i can help :-)

[chicoxyzzy]

That's great!

I've also updated the data and published a new version.