Repository navigation
[opencode] docs: add vanilla-first policy to backstage-upgrade skill - #103
Merged
Merged
Conversation
Upgrades should reconcile with the create-app template via the upgrade-helper diff instead of accumulating drift. Documents when local edits may be kept and prefers one-line config fixes over vendored files or pins when upstream breaks. 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
Adds a vanilla-first policy to the
backstage-upgradeskill and reworks the template-reconciliation step around it.Why
Upgrades were drifting from the vanilla
create-apptemplate over time. The upgrade-helper diff was listed as a manual check rather than a default action, so template changes accumulated as optional. The policy makes staying close to vanilla the default: apply template changes, keep local edits only for deliberate customisations (theming,@internal/*plugins, RBAC, Plausible), and prefer one-line config fixes over vendored files, pins, or extra Docker layers when upstream breaks - the exact trade-off we just hit with thegotpatch.Validation
Docs-only change to a skill file. No build impact; lint still green from the working tree.