Release prep 0.13.0-beta: changelogs + lock non-published packages#58
Merged
Conversation
- Add ## 0.13.0-beta CHANGELOG entries for the 9 publishable packages (dart_node_core: filesystem + child-process interop; dart_node_mcp: streamable HTTP transport + server capabilities; the rest maintenance) - Lock dart_jsx, dart_node_vsix, dart_node_coverage with publish_to: none so release tagging can never publish or alter them (placeholder versions kept)
MelbourneDeveloper
added a commit
that referenced
this pull request
Jun 9, 2026
## TLDR Prepares the `0.13.0-beta` release: adds changelog entries for the 9 publishable packages and locks the non-published packages so release tagging can't touch them. ## What Was Changed? - **CHANGELOG `## 0.13.0-beta`** for all 9 publishable packages. Only three changed since `0.12.0-beta`: `dart_node_core` (filesystem `fs` bindings + child-process interop), `dart_node_mcp` (streamable HTTP transport + server capabilities), `dart_node_ws` (test-only). The other six are maintenance. - **`publish_to: none`** added to `dart_jsx`, `dart_node_vsix`, `dart_node_coverage` — they had no publish guard and are not in the release config, so this guarantees the `Release/0.13.0-beta` tag can never publish or alter them. Versions kept as placeholders. ## Why `0.12.0-beta` is already live on pub.dev; `0.13.0-beta` is the next version. The release skill requires a `## 0.13.0-beta` changelog entry per publishable package before tagging. Package version bumps are intentionally NOT made here — CI stamps them on the ephemeral release branch from the tag. ## Breaking Changes - [x] None — changelog + publish-guard metadata only.
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.
TLDR
Prepares the
0.13.0-betarelease: adds changelog entries for the 9 publishable packages and locks the non-published packages so release tagging can't touch them.What Was Changed?
## 0.13.0-betafor all 9 publishable packages. Only three changed since0.12.0-beta:dart_node_core(filesystemfsbindings + child-process interop),dart_node_mcp(streamable HTTP transport + server capabilities),dart_node_ws(test-only). The other six are maintenance.publish_to: noneadded todart_jsx,dart_node_vsix,dart_node_coverage— they had no publish guard and are not in the release config, so this guarantees theRelease/0.13.0-betatag can never publish or alter them. Versions kept as placeholders.Why
0.12.0-betais already live on pub.dev;0.13.0-betais the next version. The release skill requires a## 0.13.0-betachangelog entry per publishable package before tagging. Package version bumps are intentionally NOT made here — CI stamps them on the ephemeral release branch from the tag.Breaking Changes