Access to publish npm packages

[ertrzyiks]

Hey team, I maintain a couple of hexo plugins and while I still have admin rights to their repos I lost access to my NPM account hence I also lost ability to publish new versions of the plugins.

My account was: https://www.npmjs.com/~ertrzyiks

The packages I maintain and I would to be able to publish:

• https://www.npmjs.com/package/hexo-fontawesome
• https://www.npmjs.com/package/hexo-filter-responsive-images
• https://www.npmjs.com/package/hexo-filter-lqip

My new account is: https://www.npmjs.com/~ertrzyiks2

The context for my request is: hexojs/hexo-fontawesome#303

[SukkaW]

cc @yoshinorin

BTW, we are now using npm trusted publish. Might wanna set up that and publish npm packages via GitHub Actions here.

[yoshinorin]

@ertrzyiks
According to hexojs/hexo-fontawesome#303, it seems you already contacted npm support but were unable to recover your account. Is there no way to recover it? Unfortunately, hexo-fontawesome has no npm Collaborators set up, so we are unable to change the publish settings on our side...

That said, we could help assist you in communicating with npm support. Do you think that could help?

[ertrzyiks]

@SukkaW sounds cool, I will try to set it up

@yoshinorin the account is not recoverable and I was instructed to create a new one, the response from NPM support:

• Create a new npm account: https://www.npmjs.com/signup
• Ask any organization admins to invite your new account to the org and re-grant package access
• For packages you own under an organization, an org admin can add your new account as a maintainer
• Packages owned solely by your old personal account can’t be transferred without access to that account

so the account is gone and we can do nothing about it. The package might be still recoverable and for that I could reach out to the NPM support.

[yoshinorin]

@ertrzyiks
As I mentioned in https://github.com/orgs/hexojs/discussions/5748#discussioncomment-16330375, hexo-fontawesome is not managed under the hexojs organization and has no Collaborators set up, so we are unable to change the package settings on our side...

As for the other two packages, I didn't have permission to add you as a Collaborator. However, as @SukkaW suggested, I was able to set up Trusted Publishing via GitHub Actions. So these two packages can now be published via GitHub Actions (I'll open a PR for this later).

[yoshinorin]

I'll open a PR for this later

Submitted.

• ci: enable trusted publishing hexo-filter-lqip#192
• ci: enable trusted publishing hexo-filter-responsive-images#241