docs: record how the v2.32.6 archive was actually produced - #322
Merged
Conversation
The release entry described the export as if it had run locally. It did not: R8 crashed the daemon twice on native-memory starvation, and the AAB and mapping in D:\Build were downloaded from the tag job instead. That substitution is sound -- same commit, same task, same signing key -- but a log that reports the happy path it did not take is the drift this file exists to prevent. Also recorded the PowerShell quoting trap on -P properties, and why the launch-smoke failure on #321 is the known emulator flake rather than a regression. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
1 participant
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.
The v2.32.6 entry in HISTORY.md described the release export as if it had run locally. It did not.
:app:exportReleaseToBuildDrivecrashed the Gradle daemon twice inside:app:minifyReleaseWithR8—Native memory allocation (malloc) failed, first at-Xmx2048mand again at-Xmx1536m, with roughly 1.7 GB free. The tag job had already built both artifacts, somarkleaf-v2.32.6-vc128.aaband.mapping.txtinD:\Buildcame from run 31891151897, with the notes file assembled from the seven128.txt.verify-release-export.ps1passes on the result and the AAB carries the release certificate, so the substitution is sound — same commit, same task, same key — but the log should say so.Two other things worth having written down:
-Pmarkleaf.requireReleaseSigning=truehas to be quoted from PowerShell. Unquoted it is split, and Gradle reportsTask '.requireReleaseSigning=true' not found, which reads like a missing task rather than a mangled argument.launch-smokefailing on release: v2.32.6 (versionCode 128) #321 is the known emulator flake (Broken pipe (32), thenCan't find service: package), not a regression: the same job passed on fix: proper icon sizing in drawables #318 with identical app code.🤖 Generated with Claude Code