Fix block lists and polish the console for v1.0.1 - #143
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.
Hagezi Pro subscriptions used a retired URL, mobile catalog controls had inconsistent alignment, and development builds could replace themselves with a published release. This patch restores the feed, preserves existing cached block lists during migration, and blocks release checks and installation for development builds.
Validation:
go mod verify,go tool mage verify,go tool mage race,go tool govulncheck ./...,go tool mage releaseCheck,go tool mage releaseSmoke, andgo tool mage dockerSmokepass. The container checks verify that snapshots retain their image build, released containers use staged updates, and the HTTP health endpoint starts. The vulnerability scan reports no affected code paths or imported packages. Mobile layout and both 12/24-hour preferences were checked in the demo, and the Compose configuration was validated.The release workflow owns version tags and publication after this change reaches
mainand its required checks pass.