Skip to content
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.

access: grant / revoke now work on unscoped packages #126

Merged
merged 1 commit into from
Nov 19, 2015

Conversation

othiym23
Copy link
Contributor

Asssuming all the privileges line up.

r: @zkat

Asssuming all the privileges line up, allow these requests through to
the registry.

Credit: @othiym23
PR-URL: #126
@othiym23 othiym23 force-pushed the othiym23/grant-revoke-unscoped branch from f4e4624 to f43d368 Compare November 19, 2015 01:16
@othiym23 othiym23 merged commit f43d368 into master Nov 19, 2015
othiym23 added a commit to npm/npm that referenced this pull request Nov 19, 2015
othiym23 added a commit to npm/npm that referenced this pull request Nov 19, 2015
Allow access grants, revocations, and enumerations to be requested for
unscoped packages, because the version of teams and orgs that shipped
for the primary registry changed somewhere along the way to allow orgs
to own unscoped packages.

Credit: @othiym23
PR-URL: npm/npm-registry-client#126
othiym23 added a commit to npm/npm that referenced this pull request Nov 20, 2015
Allow access grants, revocations, and enumerations to be requested for
unscoped packages, because the version of teams and orgs that shipped
for the primary registry changed somewhere along the way to allow orgs
to own unscoped packages.

Credit: @othiym23
PR-URL: npm/npm-registry-client#126
@zkat zkat deleted the othiym23/grant-revoke-unscoped branch March 8, 2018 06:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant