Triage failing Renovate updates and constrain unsupported upgrades #49

Open
opened 2026-11-21 12:18:09 +00:00 by martin · 0 comments
Owner

Summary

Triage failing Renovate updates: fix updates that are compatible with the current Backstage/toolchain, and narrowly disable updates that are unsupported or would introduce unapproved breaking changes through renovate.json.

Context

The Dependency Dashboard (#8) contains multiple outstanding upgrades, including major React, React Router, TypeScript, jsdom, better-sqlite3, and Backstage updates. Their compatibility and failure reasons need to be assessed individually against current Backstage peer constraints and repository checks; do not assume that every Renovate failure is an upstream incompatibility.
Issue #34 previously tracked a broad dependency-update pass and is closed. This issue focuses on diagnosing current failures and maintaining explicit Renovate policy for upgrades that should not be proposed yet.

Scope

  • Review outstanding Renovate PRs and classify each as compatible and fixable, unsupported/incompatible for now, or blocked pending upstream work.
  • Fix compatible updates and make only the related changes needed to keep the application and validation suite working.
  • Add narrowly scoped package rules to renovate.json for updates that must be disabled or deferred, recording the affected package/update scope and the reason.
  • Preserve updates that remain supported, including security updates where applicable; avoid blanket disabling of all major or dependency updates.
  • Revisit deferred rules when the relevant Backstage peer range, upstream release, or repository validation changes.

Acceptance criteria

  • Every outstanding failing Renovate update in the reviewed set has a recorded diagnosis and disposition.
  • Compatible updates selected for adoption are fixed and pass the relevant repository checks.
  • renovate.json suppresses only identified unsupported or explicitly deferred updates, with each rule's scope and rationale documented.
  • Supported non-major and security updates remain enabled unless a concrete incompatibility is recorded.
  • Renovate configuration validation passes, and a subsequent run does not recreate updates covered by the new rules.
  • The Dependency Dashboard reflects the resulting actionable set rather than repeatedly listing known-incompatible updates.
  • #8 (Renovate Dependency Dashboard; source for current update PRs)
  • #34 (closed earlier issue for a broad dependency update pass; context only)
## Summary Triage failing Renovate updates: fix updates that are compatible with the current Backstage/toolchain, and narrowly disable updates that are unsupported or would introduce unapproved breaking changes through renovate.json. ## Context The Dependency Dashboard (#8) contains multiple outstanding upgrades, including major React, React Router, TypeScript, jsdom, better-sqlite3, and Backstage updates. Their compatibility and failure reasons need to be assessed individually against current Backstage peer constraints and repository checks; do not assume that every Renovate failure is an upstream incompatibility. Issue #34 previously tracked a broad dependency-update pass and is closed. This issue focuses on diagnosing current failures and maintaining explicit Renovate policy for upgrades that should not be proposed yet. ## Scope - Review outstanding Renovate PRs and classify each as compatible and fixable, unsupported/incompatible for now, or blocked pending upstream work. - Fix compatible updates and make only the related changes needed to keep the application and validation suite working. - Add narrowly scoped package rules to renovate.json for updates that must be disabled or deferred, recording the affected package/update scope and the reason. - Preserve updates that remain supported, including security updates where applicable; avoid blanket disabling of all major or dependency updates. - Revisit deferred rules when the relevant Backstage peer range, upstream release, or repository validation changes. ## Acceptance criteria - [ ] Every outstanding failing Renovate update in the reviewed set has a recorded diagnosis and disposition. - [ ] Compatible updates selected for adoption are fixed and pass the relevant repository checks. - [ ] renovate.json suppresses only identified unsupported or explicitly deferred updates, with each rule's scope and rationale documented. - [ ] Supported non-major and security updates remain enabled unless a concrete incompatibility is recorded. - [ ] Renovate configuration validation passes, and a subsequent run does not recreate updates covered by the new rules. - [ ] The Dependency Dashboard reflects the resulting actionable set rather than repeatedly listing known-incompatible updates. ## Related - #8 (Renovate Dependency Dashboard; source for current update PRs) - #34 (closed earlier issue for a broad dependency update pass; context only)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Personal/backstage#49
No description provided.