Repository navigation
Conversation
✅ Deploy Preview for steady-daffodil-d78dee ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This was referenced Nov 11, 2026
This branch was successfully deployed
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.
The manifest reference teaches legacy upstream fields, a string-valued global-env flag and an unsupported UPnP field name. Its mixed-service example also makes service references difficult to follow.
Replace it with a coherent manifest/Compose pair; document
upstream[], short global-env names, service-reference checks,upnpDisable, supported update warnings and literal-dot versions. Explain template identity and positional array inheritance in the development guides. Preserve current front matter/navigation and the old UPnP anchor.Companion changes: SDK validation and Shared schema/runtime. The reference explicitly identifies the shared-schema release needed for legacy global-env objects. Related UPnP documentation proposal: #475.
Validation:
npm cifails because optional platform packages are missing from the existing lockfile. The build usednpm install --ignore-scripts --lockfile-version=2in an isolated worktree, with the lockfile restored before commit. Existing unrelated broken-anchor warnings remain.