fix: change npm profile to create tokens with GAT support#8706
fix: change npm profile to create tokens with GAT support#8706owlstronaut merged 3 commits intolatestfrom
Conversation
owlstronaut
changed the title
owlstronaut
force-pushed
the
owlstronaut/gat-create-support
branch
from
dfcfec9 to
ff27b2a
Compare
owlstronaut
changed the title
owlstronaut
force-pushed
the
owlstronaut/gat-create-support
branch
2 times, most recently
from
e1966ed to
12e237f
Compare
| Show extended information in \`ls\`, \`search\`, and \`help-search\`. | ||
| `, | ||
| }), | ||
| name: new Definition('name', { |
There was a problem hiding this comment.
I think we may want to namespace a few of these to gat-, if not all of them.
wraithgar
force-pushed
the
owlstronaut/gat-create-support
branch
from
12e237f to
a0b368f
Compare
|
Updated to just use npm-registry-fetch. Tests still need updating. |
wraithgar
force-pushed
the
owlstronaut/gat-create-support
branch
2 times, most recently
from
2010c96 to
553d993
Compare
wraithgar
changed the title
clean up tests too, combine all the extras into one test.
wraithgar
force-pushed
the
owlstronaut/gat-create-support
branch
from
553d993 to
709425b
Compare
|
4 participants
This pull request introduces extensive enhancements to the npm token management command, adding support for creating Granular Access Tokens (GATs) with fine-grained permissions. It updates the CLI interface, configuration, and documentation to allow users to specify token details such as name, description, expiration, package/scope/org restrictions, permission levels, and bypassing two-factor authentication. The changes also improve error messaging and ensure all new options are reflected in the config and docs.
Needs npm/npm-profile#175 changes/release before this will work.