search

Aller-Couleur / handlebars-i18n

handlebars-i18next.js adds the internationalization features of i18next and Intl to handlebars.js
Other
16 stars 6 forks source link

The automated release is failing 🚨 #27

Closed github-actions[bot] closed 3 years ago

github-actions[bot] commented 3 years ago

:rotating_light: The automated release from the master branch failed. :rotating_light:

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default " Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

dargmuesli commented 3 years ago

Hmm, @fwalzel, somehow the NPM token seems to be incorrect. Could you try removing and readding it, making sure there are not whitespaces before and after the token string and that the token actually has push permissions to the npm registry?

and...

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default " Authorization and writes" level.

fwalzel commented 3 years ago

Okay, I removed and re-added the NPM_TOKEN making absolutely sure, there were no white spaces etc. Hope this works for you! BTW: I generated the token with $ npm token create, but as far as I know there are no arguments/ options to be set for special push permissions to the registry. It should work automatically with the token generating.

Am 28.04.2021 um 23:37 schrieb Jonas Thelemann @.***>:

Hmm, @fwalzel https://github.com/fwalzel, somehow the NPM token seems to be incorrect. Could you try removing and readding it, making sure there are not whitespaces before and after the token string and that the token actually has push permissions to the npm registry?

and...

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default " Authorization and writes" level.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Aller-Couleur/handlebars-i18n/issues/27#issuecomment-828796519, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUNJVIONQRSZJRI4MQ2CDLTLB52HANCNFSM43X35SYQ.

fwalzel commented 3 years ago

hm, just seeing this: automation is set to false (and can not be generated with argument 'true' via the cli), might this affect us? Bildschirmfoto 2021-04-29 um 19 07 52

dargmuesli commented 3 years ago

No, it works now! :partying_face: The first automatic version of handlebars-i18n has successfully been released, congratulations! Comments notifying about this release have been added to all related issues and pull requests, which might have resulted in a few notifications / mails.

fwalzel commented 3 years ago

Nice! Thank you.

fwalzel commented 3 years ago

The only thing is, we are back on v1.0.0. Will this effect user's version management?

dargmuesli commented 3 years ago

Oh, I see. There was no previous version tag in Git so it started with version 1. I'll try to fix that now.

dargmuesli commented 3 years ago

Ok, we're at v1.2.0 now. If you can, you could revoke release v1 from npm https://www.npmjs.com/package/handlebars-i18n/v/1.0.0. I don't know if that one never existed or was now overwritten, I'm sorry about that!

fwalzel commented 3 years ago

All fine. I unpublised @1.0.0. Thanks for the great job you did!

Am 29.04.2021 um 21:31 schrieb Jonas Thelemann @.***>:

Ok, we're at v1.2.0 now. If you can, you could revoke release v1 from npm https://www.npmjs.com/package/handlebars-i18n/v/1.0.0 https://www.npmjs.com/package/handlebars-i18n/v/1.0.0. I don't know if that one never existed or was now overwritten, I'm sorry about that!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Aller-Couleur/handlebars-i18n/issues/27#issuecomment-829528844, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUNJVJDAN2X6BSOVIBQSY3TLGXYJANCNFSM43X35SYQ.

dargmuesli commented 3 years ago

You're welcome!

fwalzel commented 3 years ago

Hi Jonas, did you receive my off-topic mail from 21-05-11 :)

Am 30.04.2021 um 00:54 schrieb Jonas Thelemann @.***>:

You're welcome!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Aller-Couleur/handlebars-i18n/issues/27#issuecomment-829647200, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUNJVPHTVL3LSOQAIF2WL3TLHPUFANCNFSM43X35SYQ.