fix(release): enable --unstable-raw-imports for whole-workspace publish (alpha.5 republish)#138
Merged
Merged
Conversation
The JSR-safe asset embedding (with { type: 'text' } import attributes) is
rejected by the deno publish module-graph builder unless raw-imports is
enabled. A member deno.json cannot carry "unstable" (Deno only honors it in
the workspace-root config), and the root config's "unstable" does not
propagate into per-member publish graph builds.
As a result v0.0.1-alpha.5 partial-published: @netscript/fresh-ui and
@netscript/plugin failed with "The import attribute type of 'text' is
unsupported" and 6 dependents were skipped (23 of 31 members published).
Pass --unstable-raw-imports explicitly on the publish command so every
member's publish graph build enables the feature. The publish dry-run path
does not enforce this restriction, which is why publish:dry-run stayed green
while the real publish failed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014gW4zfhMMQU6txC828ijct
This was referenced Jun 27, 2026
Closed
13 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix partial publish of v0.0.1-alpha.5
The v0.0.1-alpha.5 JSR publish partial-failed: 23 of 31 members published, but
@netscript/fresh-uiand@netscript/pluginfailed and 6 dependents (incl.@netscript/cli) were skipped.Root cause
These members use JSR-safe asset embedding —
with { type: 'text' }import attributes (#135). Thedeno publishmodule-graph builder rejects those attributes unlessraw-importsis enabled:deno.jsoncannot carry"unstable"— Deno only honors it in the workspace-root config ("unstable" field can only be specified in the workspace root deno.json file)."unstable": ["raw-imports"]does not propagate into per-member publish graph builds.deno publish --dry-rundoes not enforce this restriction, sopublish:dry-runstayed green while the real publish failed — a true dry-run blind spot.Fix
Pass
--unstable-raw-importsexplicitly on thedeno publishcommand in.llm/tools/publish-workspace.tsso every member's publish graph build enables the feature. The flag is recognized bydeno publish2.9.0.Why this is safe to re-publish
deno publishskips versions already on the registry, so re-running after a partial publish is idempotent — the 23 already-published members are skipped; onlyfresh-ui,plugin,cli, and the 6 skipped dependents publish at alpha.5.Follow-up (tracked)
The publish dry-run gate is a blind spot for this failure class — a real-publish-equivalent preflight is tracked under the deterministic JSR release/publish e2e mechanism (#114).
🤖 Generated with Claude Code