Where does each kind of fact come from?
We read defaults and labels from the source code at the release tag, never from memory or third-party articles. The current pages match Upscayl 2.15.0 (tag v2.15.0).
| Fact | Source |
|---|---|
| Default model, scale, format, output folder, overwrite, updates, usage data | user-settings-atom.ts and index.tsx |
| Menu labels, model names, error messages | renderer/locales/en.json |
| Output file and batch folder names | image-upscayl.ts and batch-upscayl.ts |
| Installer type, publisher, macOS minimum | package.json build configuration |
| GPU requirement, SmartScreen, blur limits | README |
| GPU IDs, scale emulation, custom models, Vulkan errors | wiki Guide and Troubleshooting |
| Versions, file names, sizes | GitHub release data, refreshed daily |
| File hashes | winget manifest, Homebrew cask, or our own SHA-256 of the GitHub file |
How do we handle a new Upscayl release?
A daily job compares every source file the pages cite between the checked tag and the new one. Unchanged files let the checked version advance; a changed file stops the update until an editor re-reads it and corrects the copy. Changelog claims name the release that introduced a feature and link to its release notes.
How are corrections made?
A reported or discovered error is checked against the source file, fixed, and the page's "last verified" date is updated. We record what changed in the site's repository history. We do not accept payment for links or rankings, and we do not publish benchmark numbers we did not measure.