Dusk/Modernization-Tool
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 5 Wiki Activity

Stabilize bundled component installation #8

Merged
Dusk-92 merged 18 commits from test/stable-bundled-components into main 2026-09-03 14:42:37 +00:00
Conversation 0 Commits 18 Files Changed 6
+544 -154
Dusk-92 commented 2026-09-03 08:36:32 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Summary

  • keep SuperAPI following upstream master, while downloading the exact resolved commit SHA
  • pin branch-based GitHub downloads to their resolved commit SHA
  • use the bundled known-good No1600x1200 copy instead of following the archive repository
  • verify bundled payload size, SHA-256 and x86 PE format before installation
  • install VanillaFixes/VfPatcher and PerfBoost/settings transactionally
  • stop copying component addons globally before remote package resolution
  • clean stale transactional backups only after the live package is verified current
  • remove the manually maintained README version table and keep source links as the long-term reference
  • simplify WeirdPerformance UI attribution to by Dusk-92
  • reorganize README component/source links into evergreen categories and remove stale hardcoded component/release versions
  • merge client plugin descriptions with their upstream source links to remove duplicate lists
  • inline all remaining upstream source links into their existing README sections and remove the separate Additional Upstream Sources block
  • add regression tests and update documentation

Safety

  • draft PR only
  • no changes to main
  • no payload binaries changed
## Summary - keep SuperAPI following upstream `master`, while downloading the exact resolved commit SHA - pin branch-based GitHub downloads to their resolved commit SHA - use the bundled known-good No1600x1200 copy instead of following the archive repository - verify bundled payload size, SHA-256 and x86 PE format before installation - install VanillaFixes/VfPatcher and PerfBoost/settings transactionally - stop copying component addons globally before remote package resolution - clean stale transactional backups only after the live package is verified current - remove the manually maintained README version table and keep source links as the long-term reference - simplify WeirdPerformance UI attribution to `by Dusk-92` - reorganize README component/source links into evergreen categories and remove stale hardcoded component/release versions - merge client plugin descriptions with their upstream source links to remove duplicate lists - inline all remaining upstream source links into their existing README sections and remove the separate Additional Upstream Sources block - add regression tests and update documentation ## Safety - draft PR only - no changes to main - no payload binaries changed
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Dusk
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Dusk/Modernization-Tool#8
Delete Branch "test/stable-bundled-components"

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?