chore(xml-tools): maintenance release from new monorepo location - #634
Merged
Merged
Conversation
Contributor
Build ReportPlease note:
|
jacob-kreyenbuehl
approved these changes
Sep 24, 2026
deekshas8
reviewed
Sep 24, 2026
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
3 participants
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.
What
Adds a changeset to release the 9 publishable
@xml-tools/*packages from their new monorepo location.Why
The migration PR (#620) relocated xml-tools into app-studio-toolkit but shipped changeset-free, as migrations do. This is the separate maintenance release, matching the vscode-logging (#590) and feature-toggle-node (#618) pattern. Pure relocation, so a patch.
Behaviour
On merge, the Release workflow opens a Version PR that bumps each
@xml-tools/*package one patch (e.g.@xml-tools/ast5.1.0 → 5.1.1) and writes changelogs. Nothing publishes until that Version PR is merged. No functional code changes. The privatexml-toolkitextension bumps to 1.3.1 via the internal-dependency cascade (it is not published).Verified locally:
changeset versionbumps only xml-tools packages, each by one patch, no cross-project cascade.