Housekeeping for the prometheus ownership transfer

[jdmarshall]

• Land some PRs that have been stuck (particularly the matching data storage change for the PRs that have already landed)
• Publish version "1" I propose 0.16.0
• Deprecate prom-client on npmjs.org
• The Markdown needs updating
• examples need to be updated
• benchmarks need to be updated

I think the benchmarks will be okay, other than the need for a version number shift.

[krajorama]

Yes, name is client_js , since prometheus has client_java, client_golang, client_rust , etc.

For us to land the PRs, I think we need you @jdmarshall and @SimenB to have maintainer rights and be able to approve and merge PRs. Have you received the invitation from prometheus org? please accept it.

About the version: the transfer kept the releases as well, so at least in the repo we are already at v15.3.1. In light of that would you want 0.16.0 ? Or maybe go with v16.0.0-alpha.1 / v16.0.0-rc.1 ?

[slagiewka]

I'm not sure if this should be a part of the initial housekeeping, but once the next stable @prometheus/client... package is published old package can be marked as deprecated and point to the new release. https://docs.npmjs.com/deprecating-and-undeprecating-packages-or-package-versions

[jdmarshall]

I think @siimon may have to do that, I don't think the rest of us were ever given admin access to npmjs.com

[jdmarshall]

Which reminds me. If there's not already an account suitable for admin on npmjs.com, do you want one of us to own it or do you want to take care of that?

[siimon]

Just let me know when you are ready and I'll publish a deprecation for prom-client!

[siimon]

Also, I think the docs needs to be updated too so it points to a correct url

[zbjornson]

I have package admin access on npm and can help with the migration/deprecation there as well.

[krajorama]

I've talked to Prometheus team and we've recently switched to https://docs.npmjs.com/trusted-publishers for Prometheus. So I'll set that up for this repo, which should allow us to publish releases from a workflow. I suggest to make the workflow trigger on "tag" and use immutable tags. This should take care of new releases, and we'll ask kindly Simon/Zach to deprecate the old ones once we're ready.

UPDATE: seems like I cannot set up trusted publishing for a non existent package. So we'll have to prep something that I publish next to https://www.npmjs.com/package/@prometheus-io/lezer-promql as https://www.npmjs.com/package/@prometheus-io/client_js . I've set up access for myself.

[thegu5]

https://npmx.dev/package/setup-trusted-publishing can be used to publish a dummy package

[jdmarshall]

@krajorama It's almost ceremonial that you do the first publish and then we can go from there. Now where did I leave that bottle of champagne...

[jdmarshall]

I think there's a couple PRs we want to gather up for a 0.16 and we can let you know when trunk is ready for a publish, then work from there.