Repository navigation
[opencode] feat: upgrade Backstage from 1.53.1 to 1.55.3 - #100
Merged
Merged
Conversation
Runs yarn backstage-cli versions:bump and refreshes the yarn plugin and lockfile. Adds the got patch from the yarn berry repo that @yarnpkg/core@4.9.2 (pulled in by @backstage/cli-module-package-manager-yarn) references but does not ship in its npm tarball, fixing the ENOENT on yarn install. Co-authored-by: opencode-agent[bot] <219766164+opencode-agent[bot]@users.noreply.github.com>
johnnyhuy
marked this pull request as ready for review
October 3, 2026 00:02
The Docker build and run stages copy .yarn/plugins/ but not .yarn/patches/, so yarn install failed in-container with ENOENT on the vendored got patch. Co-authored-by: opencode-agent[bot] <219766164+opencode-agent[bot]@users.noreply.github.com>
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
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
Upgrades the Backstage monorepo from 1.53.1 to 1.55.3, the current latest stable release, and unblocks
yarn installalong the way.Why
The portal was pinned to Backstage 1.53.1 while 1.55.3 is the current stable line. Staying behind means missing framework fixes and features, and each release we skip makes the next upgrade diff larger. This is the routine sweep to keep the repo current.
The install blocker and its root cause
yarn backstage-cli versions:bumpsucceeded, but its follow-upyarn installfailed during the resolution step:Root cause: the 1.55.x line pulls in
@backstage/cli-defaults->@backstage/cli-module-package-manager-yarn->@yarnpkg/core@^4.9.1. Yarn 4.9.2 published@yarnpkg/corewith agotdependency using thepatch:protocol, but the patch file itself only exists in the yarn berry monorepo and is not shipped in the npm tarball. Every consumer of that package hits an ENOENT unless they vendor the patch.Fix: vendor the exact patch file from the public yarn berry repo into
.yarn/patches/, so Yarn applies the upstream promise-settle fix togotas intended. No hand-written patch content, no unpatchedgotdowngrade.Changes
backstage.json1.53.1 -> 1.55.3.yarnrc.ymlspec refreshed to the 1.55.3 pluginyarn.lockre-resolved for the 1.55.3 release line.yarn/patches/got-npm-11.8.2-c1eb105458.patchadded (fromyarnpkg/berry)Validation
mise run lintpasses (all workspaces type-checked)mise run testpasses: 9 tests passed, 1 skipped, 2 of 3 suites ranmain(homepage onboarding + release commits) and re-verified after the rebase