Skip to content
This repository has been archived by the owner on Jul 25, 2018. It is now read-only.

Release version 0.3 #3

Open
Avaq opened this issue Jan 11, 2017 · 12 comments
Open

Release version 0.3 #3

Avaq opened this issue Jan 11, 2017 · 12 comments
Assignees

Comments

@Avaq
Copy link
Contributor

Avaq commented Jan 11, 2017

To publish the changes made in #2

@Avaq
Copy link
Contributor Author

Avaq commented May 17, 2017

😕

@davidchambers
Copy link
Member

$ npm owner ls fantasy-states | cut -d ' ' -f 1
puffnfresh
joneshf

Either @puffnfresh or @joneshf should run npm access grant read-write fantasyland:owners fantasy-states as requested in fantasyland/daggy#10 (comment). I will then integrate xyz and release v0.3.0.

@joneshf
Copy link
Member

joneshf commented May 18, 2017

I'll grab thta ina bit.

@joneshf joneshf self-assigned this May 18, 2017
@joneshf
Copy link
Member

joneshf commented May 19, 2017

~ npm whoami                                                   
joneshf
➜  ~ npm team ls fantasyland:owners                               
[
  "safareli",
  "raimohanska",
  "simonrichardson",
  "kennknowles",
  "trevorbasinger",
  "joneshf",
  "jaforbes",
  "mudge",
  "davidchambers",
  "raynos",
  "puffnfresh",
  "drboolean",
  "robotlolita"
]
➜  ~ npm access ls-collaborators fantasy-states
{
  "joneshf": "read-write",
  "puffnfresh": "read-write"
}
➜  ~ npm access grant read-write fantasyland:owners fantasy-states
npm ERR! code E403
npm ERR! Forbidden : -/team/fantasyland/owners/package

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/joneshf/.npm/_logs/2017-05-19T15_19_47_018Z-debug.log

🤷‍♂️

@davidchambers
Copy link
Member

That's odd. Hardy, could you try granting access to me specifically rather than to the team? That'll help with the diagnosis.

@joneshf
Copy link
Member

joneshf commented May 27, 2017

Sorry. Totally dropped the ball. Adding you now.

@joneshf
Copy link
Member

joneshf commented May 27, 2017

Actually, I don't know how to do that...

@davidchambers
Copy link
Member

Could you try npm owner add davidchambers fantasy-states?

@joneshf
Copy link
Member

joneshf commented May 28, 2017

~ npm owner add davidchambers fantasy-states
+ davidchambers (fantasy-states)
➜  ~ npm access ls-collaborators fantasy-states
{
  "davidchambers": "read-write",
  "joneshf": "read-write",
  "puffnfresh": "read-write"
}

@davidchambers
Copy link
Member

Thanks, Hardy. I can't perform the action either. According to npm/npm#15667 (comment) only the person who initially published the package can add it to an organization.

@puffnfresh, could you run npm access grant read-write fantasyland:owners fantasy-states?

@Avaq
Copy link
Contributor Author

Avaq commented Aug 4, 2017

🗓️

@joneshf
Copy link
Member

joneshf commented Dec 11, 2017

There's nothing for me to do here, assigning to @puffnfresh.

@joneshf joneshf assigned puffnfresh and unassigned joneshf Dec 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants