chore(guided-development): maintenance release from new monorepo location - #609
Merged
jacob-kreyenbuehl merged 1 commit intoSep 10, 2026
Merged
Conversation
…tion Signed-off-by: Jacob Kreyenbuehl <jacob.kreyenbuehl@sap.com>
Contributor
Build ReportPlease note:
|
rolanbadrislamov
approved these changes
Sep 10, 2026
jacob-kreyenbuehl
deleted the
changeset/guided-development-maintenance-release
branch
September 10, 2026 13:55
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 guided-development
fixedgroup from its new monorepo home (projects/guided-development):guided-developmentandguided-development-frontend.Why
The migration (#601) relocated the packages without releasing them. This is the separate post-merge release step, matching the vscode-logging (#590) and yeoman-ui (#535) pattern. It is a pure relocation, so a patch, and it validates 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 version together (fixed group) and the backend VSIX is uploaded to its GitHub Release for
bas-tools.Verified locally with the full
pnpm run ci:versiondry-run: only the two guided-development packages bump (0.2.8 and 0.1.2), no cascade into other fixed groups, lockfile step clean.@sap_oss/guided-development-typesstays inignore(deferred, tracked separately).