chore(release): bump workspace to 0.0.1-alpha.4#132
Merged
Conversation
Whole-workspace version bump 0.0.1-alpha.3 -> 0.0.1-alpha.4 across all 32 members + the workspace-root deno.json. Cuts the alpha.4 release that exercises the three alpha.3 release-train fixes (#131) end-to-end: the per-field JSR settings PATCH, the Deno 2.9 --minimum-dependency-age=0 e2e installs, and the standalone-CLI @netscript/* import resolution. - `deno bump-version prerelease` bumped all 32 workspace members and (being workspace-aware) the packages/cli @netscript/{aspire,config,plugin} import ranges to ^0.0.1-alpha.4. - The workspace-root deno.json version and the 3 matching deno.lock dependency entries were bumped manually: native bump-version only touches workspace[] members, so it skips the publish:false root meta-version and the lock's dependency mirror. Validated: whole-workspace `deno publish --dry-run` succeeds (import ranges and lock are consistent; all member tarballs build). Refs #114 #116. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014gW4zfhMMQU6txC828ijct
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.
Release bump:
0.0.1-alpha.3→0.0.1-alpha.4Version-only whole-workspace bump that cuts the alpha.4 release. alpha.4 is the first publish that exercises the three alpha.3 release-train fixes (#131) end-to-end:
Apply JSR package settingsshould now applyreadmeSource/description/runtimeCompat(one PATCH per field), given an edit-scopedJSR_TOKEN.--minimum-dependency-age=0—e2e-cli-prodcan install the just-published CLI past the <24h supply-chain recency guard.@netscript/*resolution —packages/cli/deno.jsondeclares the siblingjsr:imports so a globally-installed CLIbinresolves them.What changed
deno bump-version prereleasebumped all 32 workspace members and (workspace-aware) thepackages/cli@netscript/{aspire,config,plugin}import ranges to^0.0.1-alpha.4.deno.jsonversion and the 3 matchingdeno.lockdependency entries were bumped manually — nativedeno bump-versiononly touchesworkspace[]members, so it skips thepublish:falseroot meta-version and the lock's dependency mirror. (Tooling follow-up tracked to automate this.)Diff shape
34 files: 33
deno.json(root + 32 members, version field only;clialso bumps its 3 import ranges) +deno.lock(3 lines). No source changes.Validation
deno publish --dry-runsucceeds — import ranges and lock are consistent and every member tarball builds.After merge
Tag
v0.0.1-alpha.4+ publish a GitHub Release to firepublish.yml(JSR + settings),e2e-cli-prod.yml, andpages.yml.Refs #114, #116.
🤖 Generated with Claude Code