Set Dist-Tag
npm.set_dist_tag
ActionBusiness appsconnection required
Calls the npm Registry API with the connection's credentials.
Point a dist-tag at a published version, creating the tag if needed.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- npm Registry
- Secret shape
- optional — the npm token, or {"api_token": "…"}; reads need none
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
package The package name, scope included — the slash in a scoped name is escaped for you. | string | Yes | — | — | express |
tag The dist-tag to act on, such as latest, next or beta. | string | Yes | — | — | next |
version The already-published version the tag should point at. | string | Yes | — | — | 2.1.0 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"package": "express",
"tag": "next",
"version": "2.1.0"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
package The package the tag was set on. | string | — |
tag The dist-tag that now points at the version. | string | — |
version The version the tag points at. | string | — |
{
"package": "",
"tag": "",
"version": ""
}Notes
- This is a publish: the connection needs a token with write access to the package, and the node refuses the call before it is made without one.
- A tag that reads as a version number is refused, the same way npm's own CLI refuses it.
Related npm Registry nodes
See Set Dist-Tag run in a workflow.
In a technical demo we add the npm Registry connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.