-
Notifications
You must be signed in to change notification settings - Fork 0
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
Publish package to NPM #1
Comments
Hey currently we do Not have any npm package nor organization. @JimBugwadia who should create the Organization in NPM? |
@fjogeleit, @Jaxwood, and I can also create the Organization in NPM and then transfer ownership to you, or to whoever should be the owner. |
Okay, lets to that for now |
@fjogeleit i have invited you to the NPM Organization, we need to use an access token in our Github Actions and would like to store that in a secret in the repository. We need that to be able to publish our package to NPM, currently we do not have access to add secrets - do you know who can assist us ? |
Thanks, joined the organization. @realshuting @eddycharly can one of you assist here? |
Hi @Jonas-Beck - what permissions do you need? |
@realshuting Me and @Jonas-Beck just had a look into the permissions. From the Github docs it looks like you will have to be admin on the repository to manage secrets. I'm not sure if you are OK with this? |
Not sure if you are talking about the same. @realshuting - @Jaxwood needs to be repo admin to add secrets for the github workflow. Can you grant him the repository permissions for his github user? @Jaxwood - @realshuting asked about the permissions your token needs to fulfill your GitHub action for publishing the code to NPM |
I have added you @Jaxwood as the repo admin, and configured a |
Set up a GitHub Actions pipeline to publish packages to NPM.
@fjogeleit, do you know if Kyverno already has an NPM organization, and if there are any standards we should follow regarding how we release new packages?
Previously, we have been using
lerna publish from-package
, which would release a new package version if thepackage.json
version is greater than the currently published version.The text was updated successfully, but these errors were encountered: