Repository navigation
Add Peer Pressure support and release v2.4.0 - #7
Merged
Merged
Conversation
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.
Peer Pressure now has its own installer USB workflow, including verified v1.0.477 downloads, Rock Band Blitz, and HDD homebrew extras. Aurora can be selected as the default dashboard through the upstream DashXex setting; XeLL and existing catalog entries are preserved. BadUpdate and ABadAvatar keep their existing bootstrap/homebrew paths.
The README now starts with downloads and workflow selection and covers Peer Pressure installation, Aurora setup, backups, recovery, and development checks. Add a root changelog and v2.4.0 release notes, and bump VersionPrefix to 2.4.0 so merging triggers the established release workflow.
Validation:
The dashboard picker still accepts executable utilities; documentation directs users to choose a dashboard rather than a maintenance tool. Peer Pressure requires a supported console and HDD and the upstream system backup. The release workflow rebuilds and tests both operating systems before publishing binaries and checksums.