-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Prepare next release v2.0.0 #283
Conversation
@pascalgrimaud, do we have an org wise |
@vishal423 : no we don't have it because for publishing to NPM, you need an OTP, so the NPM_TOKEN doesn't work |
@pascalgrimaud , I don't think 2FA is applicable over here. |
@vishal423 : just added you in admin quarkus team, so you can give a try Maybe it's because the project doesn't belong to JHipster NPM organization |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@pascalgrimaud , npm auto publish seems to fail due to access denied. Can you please include my name to the allowed list of contributors on npm side? |
@vishal423 : done |
Thanks. I can see the publish workflow succeeded this time.
…On Sat, 1 Apr, 2023, 10:22 am Pascal Grimaud, ***@***.***> wrote:
@vishal423 <https://github.com/vishal423> : done
—
Reply to this email directly, view it on GitHub
<#283 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD2BV4KJ5IBUU46DYUOY7V3W66X7DANCNFSM6AAAAAAWO6T6M4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@vishal423 : approved |
npm
package. It requires someone withadmin
access to configure npm token underNPM_TOKEN
GITHUB secret.2.0.0