[Eli Pinkerton (wallstop)]

DISCLOSURE: LLM-GENERATED TEXT

Why: The v0.2.0 publish still answered E404 after the Trusted Publisher registration was updated. setup-node's registry-url writes an _authToken placeholder into .npmrc, which makes npm attempt token authentication instead of the OIDC exchange trusted publishing requires.

What:

• Publish without setup-node's registry-url token placeholder
• Publish with --loglevel=http and quote npm's own debug log when the registry refuses, so the OIDC exchange answer is visible

Refs #536

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The release workflow no longer sets setup-node’s npm registry URL. The release driver enables HTTP-level npm logs and adds filtered details from the newest npm debug log to publication failure messages. Tests and release documentation reflect these changes.

Changes: NPM publishing

Layer / File(s)	Summary
Publishing configuration and failure diagnostics .github/workflows/release.yml, scripts/release/workflow.py, scripts/tests/test_release_workflow_driver.py, .llm/references/RELEASING.md	The workflow omits setup-node’s registry setting. The release driver uses --loglevel=http and appends up to 20 matching lines from the newest npm debug log to publish failures. Tests cover the publish command and debug-log selection. The release documentation describes the changes.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• Ambiguous-Interactive/DxVisualizer#537: This PR updates the Node/npm toolchain used by npm publication, which is also affected by the publishing configuration and diagnostics here.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts