Use Forgejo releases for Wolfskin updates and match installed versions consistently #20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fm/wolfskin-5-updater-gpt"
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?
Supersedes #17
Goal
Use Wolfskin's Forgejo releases for in-app updates and installed-version release notes.
Changes
Verification
Ran each required command once on the delivered implementation:
flock /tmp/wolfskin-gradle.lock make test: BUILD SUCCESSFUL in 1m 56s, 69 actionable tasks (26 executed, 43 up-to-date). JUnit XML: 394 tests, 0 failures, 0 errors, 0 skipped, including all 17 updater tests and one temporary HTTP smoke probe.flock /tmp/wolfskin-gradle.lock make apk-debug: BUILD SUCCESSFUL in 58s, 73 actionable tasks (16 executed, 57 up-to-date).Limits and risk
No signed release, device installation, playback, or TV UI verification performed. Debug APK intentionally uses the MPV stub and omits optional codec decoders. Forgejo fixtures are schema-shaped synthetic responses, not recorded published releases. Release attachments must be renamed as documented. Lookup remains limited to 50 releases.
AI-assisted implementation and pull-request description.
Closes justinzeus/wolfskin#5
Code review (claude): approve. Reviewed SHA
1715041df3. Both PR 17 findings fixed: installed-release lookup now uses ordering equivalence (absent vs zero count and hash abbreviation match, different counts do not), and positive Wolfskin debug/release-suffixed asset tests were added alongside the retained negative upstream-asset tests. README upload-name note matches Gradle output names. make test: 393 tests, 0 failures.