--- title: Opt-in dist-tag permissions for npm trusted publishing description: npm trusted publishing configurations can now be granted an opt-in permission to manage dist-tags, such as promoting a version to latest or updating next and... canonical: https://daily.dev/posts/opt-in-dist-tag-permissions-for-npm-trusted-publishing-rabyo2ifn twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Opt-in dist-tag permissions for npm trusted publishing | daily.dev og:description: npm trusted publishing configurations can now be granted an opt-in permission to manage dist-tags, such as promoting a version to latest or updating next and... og:url: https://daily.dev/posts/opt-in-dist-tag-permissions-for-npm-trusted-publishing-rabyo2ifn og:image: https://api.daily.dev/og/posts/RabYO2IFN.png og:image:alt: Opt-in dist-tag permissions for npm trusted publishing og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Opt-in dist-tag permissions for npm trusted publishing **[GitHub Changelog](https://daily.dev/sources/github_updates)** · 1 min read · 0 upvotes · 0 comments ## Summary npm trusted publishing configurations can now be granted an opt-in permission to manage dist-tags, such as promoting a version to latest or updating next and beta pointers, using short-lived OIDC credentials instead of a long-lived access token. The new 'Allow npm dist-tag' setting defaults to off for all configurations, is independent of publish permissions, and existing token-based dist-tag workflows continue to work unchanged. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Can npm trusted publishing manage dist-tags like latest, next, and beta without an access token? Yes, npm trusted publishing configurations can now be granted an opt-in 'Allow npm dist-tag' permission that authorizes dist-tag operations using short-lived OIDC credentials instead of a long-lived access token. It defaults to off for both new and existing configurations, and is independent of publish permissions, so a staging-only configuration can also receive it. _Maintainers eliminating long-lived npm tokens can track publishing security changes like this on daily.dev._ ### Do I still need an npm access token to update dist-tags after enabling trusted publishing? No, once the new 'Allow npm dist-tag' permission is enabled on a trusted publishing configuration, dist-tag operations such as promoting a version to latest or updating next and beta pointers can be authorized through OIDC tokens alone. Existing token-based dist-tag management still works unchanged for configurations that don't opt in. _Teams moving toward token-free npm publishing can follow workflow changes like this on daily.dev._ ## Similar posts on daily.dev - [Multiple trusted publishing configurations for npm](https://daily.dev/posts/multiple-trusted-publishing-configurations-for-npm-paxb4vogc) · GitHub Changelog · 0 upvotes · 0 comments - [npm Introduces minimumReleaseAge and Bulk OIDC Configuration](https://daily.dev/posts/npm-introduces-minimumreleaseage-and-bulk-oidc-configuration-tw6gntfnf) · Socket · 0 upvotes · 0 comments - [npm bulk trusted publishing config and script security now generally available](https://daily.dev/posts/npm-bulk-trusted-publishing-config-and-script-security-now-generally-available-3xmurnyg7) · GitHub Changelog · 0 upvotes · 0 comments - [npm trusted publishing now supports CircleCI](https://daily.dev/posts/npm-trusted-publishing-now-supports-circleci-wltcia5ym) · GitHub Changelog · 0 upvotes · 0 comments --- Tags: [#security](https://daily.dev/tags/security), [#javascript](https://daily.dev/tags/javascript), [#authentication](https://daily.dev/tags/authentication), [#npm](https://daily.dev/tags/npm) [View this post on daily.dev](https://daily.dev/posts/opt-in-dist-tag-permissions-for-npm-trusted-publishing-rabyo2ifn) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Opt-in dist-tag permissions for npm trusted publishing","url":"https://daily.dev/posts/opt-in-dist-tag-permissions-for-npm-trusted-publishing-rabyo2ifn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/opt-in-dist-tag-permissions-for-npm-trusted-publishing-rabyo2ifn"},"datePublished":"2026-09-30T21:20:11.098Z","dateModified":"2026-09-30T21:20:27.276Z","description":"npm trusted publishing configurations can now be granted an opt-in permission to manage dist-tags, such as promoting a version to latest or updating next and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2329ae5d770d8c81edbb9564e2d80660?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2329ae5d770d8c81edbb9564e2d80660?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitHub Changelog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitHub Changelog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/15004b7835da4d89b02b115871f0f6dc","url":"https://daily.dev/sources/github_updates"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/opt-in-dist-tag-permissions-for-npm-trusted-publishing-rabyo2ifn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,javascript,authentication,npm","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitHub Changelog","item":"https://daily.dev/sources/github_updates"},{"@type":"ListItem","position":3,"name":"Opt-in dist-tag permissions for npm trusted publishing"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/opt-in-dist-tag-permissions-for-npm-trusted-publishing-rabyo2ifn#faq","mainEntity":[{"@type":"Question","name":"Can npm trusted publishing manage dist-tags like latest, next, and beta without an access token?","acceptedAnswer":{"@type":"Answer","text":"Yes, npm trusted publishing configurations can now be granted an opt-in 'Allow npm dist-tag' permission that authorizes dist-tag operations using short-lived OIDC credentials instead of a long-lived access token. It defaults to off for both new and existing configurations, and is independent of publish permissions, so a staging-only configuration can also receive it. Maintainers eliminating long-lived npm tokens can track publishing security changes like this on daily.dev."}},{"@type":"Question","name":"Do I still need an npm access token to update dist-tags after enabling trusted publishing?","acceptedAnswer":{"@type":"Answer","text":"No, once the new 'Allow npm dist-tag' permission is enabled on a trusted publishing configuration, dist-tag operations such as promoting a version to latest or updating next and beta pointers can be authorized through OIDC tokens alone. Existing token-based dist-tag management still works unchanged for configurations that don't opt in. Teams moving toward token-free npm publishing can follow workflow changes like this on daily.dev."}}]} ```