Repository navigation
AuraFlow 1.4.0: terminal wallpapers and release validation - #16
Merged
Merged
Conversation
…sses gracefully" This reverts commit e937edc.
…with source canvas
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.
AuraFlow 1.4.0 adds terminal wallpaper discovery and previews, shared playback/Scale/login controls, local Wallpaper Engine imports, download progress/cancellation, video frame blending, and Lock Screen restoration fixes.
Release validation fixes include safe wallpaper-monitor teardown, Swift 6 concurrency support, older-toolchain compatibility, correct nested signing order, portable optional media-tool checks, and separate test hosts for agent/runtime and SwiftUI window suites. Both test phases retain the complete test set and require a final passing report.
Distribution uses universal Intel/Apple Silicon archives with ad-hoc signatures. The repository owner will upload the checked DMG and ZIP manually. The optional notarized Developer ID workflow is manual and is not required for this release path.
Validation: