feat: deliver unified Xbox 360 collection platform - #19
Merged
Conversation
TrapEmAll
marked this pull request as ready for review
July 24, 2026 00:16
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.
Summary
This brings the 0.11, 0.12, 0.13, and initial 1.0 roadmap foundations together as UnityScraper 1.0.0 beta 1.
XboxUnity remains explicitly HTTP-only. No HTTPS preference or invented XboxUnity transport was introduced.
Migration notes
Migrations are additive and tracked in
app_schema_migrationswith SQLiteuser_version = 4. Existing library, knowledge, download, and backup tables are retained. The Help workspace and CLI provide consistent SQLite backup/restore operations. Metadata overrides are separate records and never overwrite imported source claims.Creating a repair plan is preview-only. Aurora database import and console inventory snapshots are read-only. FTP passwords remain memory-only and are not persisted.
Source and licensing considerations
Validation
1.0.0b1)Beta follow-up