Establish a reproducible dependency and test baseline #21
Labels
No labels
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#20 Replace Yarn with Bun before hosted deployment
Personal/backstage
#22 Add application quality gates to Woodpecker
Personal/backstage
#30 Establish a secure, persistent hosted deployment
Personal/backstage
Reference
Personal/backstage#21
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Resolve the dependency and validation uncertainty recorded in
TODO.mdbefore expanding the platform.Context
The workspace uses Backstage 1.55 and Yarn 4.13. TODO.md records peer warnings, a test run that exceeded five minutes without results, and unverified catalog contents. Establish a baseline before the planned Bun migration; this issue does not require accepting every Renovate upgrade.
Acceptance criteria
Phase
1 — Trustworthy foundation
Validated in commit
5250f5bandfc5159a; results are recorded in the progress comment andREADME.md#validation. Renovate classification is on #8.Progress: dependency and test baseline validated
Commit
5250f5b(chore: establish reproducible test and validation baseline) covers the baseline part of this issue.Root cause of the "test hang"
@backstage/cli-module-test-jestappends--watchwhenCIis unset and no--watch/--watchAll/--coverageflag is passed (node_modules/@backstage/cli-module-test-jest/dist/commands/repo/test.cjs.js:124).yarn testtherefore enters Jest watch mode and never exits; the earlier "exceeded five minutes without results" was not a failing or slow suite.yarn test:cinow passes--watchAll=false;CI=true yarn testbehaves the same. The suite finishes in about 46 s cold / 27 s warm with 1 suite and 1 test passing.Peer-dependency triage
Resolved:
@testing-library/dom9 -> 10 and@testing-library/react14 -> 16 inpackages/app, matching@backstage/frontend-test-utilsrequest ranges (^10.0.0,^16.0.0); the app render test still passes with them.@types/reactinpackages/app: it was requested by@backstage/core-componentsbut no workspace provided it.jest ~30.2.0inpackages/appandpackages/backend(@backstage/clipeer on Jest). Pinned to the root version: using^30.0.0pulled a second Jest 30.5.2 into the lockfile.Accepted and documented in
README.md#validation:react,react-dom, and@types/react18 versus@material-ui/core's^16.8.6 || ^17.0.0peer. Backstage 1.55 still depends on Material UI v4 through@backstage/core-componentsand itself requires React 18, so both ranges cannot be satisfied. Replacing@material-ui/*with@mui/*would break the workspace (application code importsmakeStylesand icons from@material-ui/*).@backstage/cli*peer notes are internal to upstream packages and not actionable here.gotstays pinned to11.8.5viaresolutionsfor the security advisory already applied in #6.yarn install --immutablenow reports only the Material UI peer mismatch.Validated command set
Node 22.23.3, Yarn 4.13.0, run to completion on this commit:
yarn install --immutableyarn tscyarn lint:allyarn prettier:checkyarn test:ci --runInBandyarn build:backendThese commands and the watch-mode note are recorded in the README "Validation" section.
TODO.mdis reconciled: the two resolved items are replaced by a pointer to the README and the remaining catalog check, which stays in #23. No generated catalog entities were touched.Remaining on this issue
.woodpecker.yaml(#22) and the Bun migration (#20), which depend on this baseline.Acceptance criteria status: peer warnings investigated and documented, suite completes with diagnostics, commands recorded, TODO reconciled. The upgrade approach is documented in README and triaged on #8; merging or closing the identified PRs is the remaining follow-up.