release: AppDock v0.2.2-beta.1 candidate - #7
Merged
Conversation
eWOOD29
marked this pull request as ready for review
August 14, 2026 15:38
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.
Scope
Prepare the first frozen AppDock Beta prerelease candidate from the accepted
developintegration state.This PR is release-preparation only. It does not create a tag, publish a GitHub Release, change Stable
main, or modify any live installation.Changes
0.2.2-beta.1;0.2.2-beta.1changelog entry covering the incident-derived updater preflight/restart-log hardening and the published-v0.2.1 helper-argument compatibility fix;Frozen source identity
233351d1caaea0541bb781cf4ba45b46c24c61628b6ea7786e9eaa962287bc012ec9812d5a05ca1c78e70a24f2869a9719607f26da039745482bf745CHANGELOG.md,appdock.py,pyproject.toml,tests/test_appdock.py,tests/test_update_channels.py,tests/test_v020.py)The disposable preparation workflow used to materialize the bounded version edits is not present in this candidate tree or branch history; the candidate is a single clean commit directly atop
develop.Exact-head CI
31810200245— SUCCESS8b6ea7786e9eaa962287bc012ec9812d5a05ca1cFrozen portable artifact
Exact Windows CI artifact
appdock-windows, artifact ID9222802077:da390823dc57bb632387d2ae19f469a5c042f2ea007192e251cc4416219c604cappdock-windows.zip: 407,173 bytes; SHA-2563b3447aa22ade2a6ad7fd571df772f6f9ad91a671f3d115b935cbda46b8059a7SHA256SUMS.txt: 86 bytes; SHA-2569641a038b3ff1a3a37adb2348cd3f5f72a6510b7dd91f1fea262fc7e316f1882RELEASE-MANIFEST.json; 0 manifest hash mismatches and no unexpected archive member0.2.2-beta.1CI independently proved the Windows and Ubuntu portable ZIP bytes match exactly.
Published-v0.2.1 compatibility control
A disposable project-lead control used
appdock.pyfrom the exact accepted v0.2.1 main-CI package (run31626216982) against the exact candidate ZIP/checksum bytes above.Observed:
v0.2.2-beta.1;0.2.1;stage_updateaccepted the exact candidate checksum, ZIP and release inventory and staged the candidate successfully;CURRENT_VERSION = "0.2.2-beta.1".This is supplemental implementation evidence; it does not replace the separate release-acceptance gate.
Remaining gates
developwithout separate explicit authorization after acceptance.v0.2.2-beta.1tag or prerelease publication without separate explicit authorization.