Where oh where are PERMISSIONS for NPM? πͺ β¨ #1004
lwasser
started this conversation in
Maintainers Corner
Replies: 2 comments 12 replies
-
|
It turns out that I figured out the owners in shell and there are 3 folks I can email to request access so we are in good shape!! Npm is nice! Ill shoot an email out tomorrow!! This might be easier than I thought it would be!
Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
10 replies
-
|
I feel like we have settled on GitHub actions now, so maybe it is safe to ignore Circle CI for the time being? That might simplify the ask from those who have access to NPM. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi friends - I left a note over in the CLI repo - I'm working on it now, and we have a lot of dep updates to do over there!!
It looks fairly straightforward, BUT we will need to get access to NPM to create releases. releases are currently done via Circle CI, but I suggest we simplify and move to GitHub Actions... EXCEPT the key for npm is saved in Circle CI right now...
Circle ci needs different permissions to clone our repo.. that should be an easy enough fix but the npm part we will need to hunt down.
@Berkmann18, do you have npm access by chance, or is this another Jake question? I pinged @gr2m about it as well.
What we can do in the meantime is set up GitHub actions and just skip deploy to npm until we have the key. then atleast tests will run consistently! I just want to have all of the info we need before emailing Jake again!
we also have some pr's from folks that look really good - i merged one that fixed some test issues tonight.
Beta Was this translation helpful? Give feedback.
All reactions