chore(vscode-logging): maintenance release from new monorepo location - #590
Merged
Merged
Conversation
First release of the vscode-logging packages from their new monorepo home projects/vscode-logging. Patch bump for logger, types and wrapper (fixed group). No functional changes; validates the release pipeline from the new location. Signed-off-by: Jacob Kreyenbuehl <jacob.kreyenbuehl@sap.com>
Contributor
Build ReportPlease note:
|
bd82
approved these changes
Aug 26, 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
2 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 that cuts a patch release of the three
vscode-loggingpackages from their new monorepo home (projects/vscode-logging):@vscode-logging/logger,@vscode-logging/types,@vscode-logging/wrapper. They are afixedgroup, so they version together to2.0.10.Why
The migration (#583) relocated the packages without releasing them. This is the separate post-merge release step (matching the mta-tools #554 and yeoman-ui #535 pattern). It is a pure relocation, so a patch, and it validates that the release pipeline works end to end from the new location.
Behaviour
On merge, the Changesets action opens a "Version Packages" PR (bumps versions, writes changelogs). No publish happens yet. When that Version PR is merged, the packages publish to npm via OIDC and GitHub Releases are created.
Because the trio sits in a
fixedgroup andupdateInternalDependenciesispatch, this cascades through the other fixed groups into a full release wave (16 packages):@vscode-logging/logger2.0.9 -> 2.0.10,types2.0.8 -> 2.0.10,wrapper2.0.9 -> 2.0.10app-studio-toolkit+@sap-devx/app-studio-toolkit-types+sample-action-client+vscode-using-workspace-api2.11.4 -> 2.11.5app-studio-remote-access4.1.2 -> 4.1.3@sap-devx/npm-dependencies-validation+vscode-dependencies-validation3.0.3 -> 3.0.4vscode-deps-upgrade-tool+vscode-using-upgrade-tool5.0.2 -> 5.0.3vscode-disk-usage2.3.3 -> 2.3.4vscode-mta-tools1.4.11 -> 1.4.12yeoman-ui+yeoman-ui-frontend-> 1.27.1Notes for review:
typesjumps 2.0.8 -> 2.0.10 (skips 2.0.9) because the fixed group lock-steps it to logger and wrapper.vscode-loggingexamples stay at their current versions (they are in the changesetignorelist), so they are not re-tagged and the upload-vsix step is not affected.