Repository navigation
·
1 commit
to main
since this release
- Documented the token scopes publishing actually needs. The previous
instruction said only "package-write scope", which authenticates fine and
then fails at publish:read:organizationandread:userare needed too.
Also notes what an install-only token needs, and that scopes cannot be
edited after a token is created. publishaccepts one of the version's archives, not only the
<name>-<version>prefix they share (D65) — so tab-completing the filename
now works instead of failing with a message that blamed a missing build.
Either form selects the same batch; naming one archive of a multi-variant
version says so before uploading. A path that looks like an archive filename
but is not one gets an error that says that, rather than suggestingpack.
Full Changelog: client-v0.8.0...client-v0.9.0