chore: prepare release v3.2.0

[arch10]

Hey, Thanks for sending a pull request!

Types of changes

What types of changes does your code introduce?

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Release preparation (version bump and release notes only, no source changes)

Description

Release preparation for v3.2.0. Three files change and no source file is touched.

app/build.gradle — defaultConfig.versionName goes from 3.1.2 to 3.2.0. A minor bump, since the span since the last release adds the ad placement priority system. version.properties is untouched; VERSION_CODE stays with the auto-bump lane.

CHANGELOG.md — new ## v3.2.0 section at the top, covering everything since chore: prepare release v3.2.0's predecessor:

• The ad placement priority system in util/AdPlacement.kt, which resolves one placement per screen from Remote Config before any request goes out, so a screen on the inline experiment never falls back to the banner on a no-fill.
• The inline 300x250 placements on History and Settings, gated behind enable_inline_ads on top of the master enable_ads switch, plus the standalone About placement gated on enable_ads alone.
• The history list recycling fix, where HistoryViewHolder.bind hid the date and border views without ever restoring them, so a recycled holder could keep them hidden.
• The Play Store rejection of the v3.1.2 upload at 685 of the 500 permitted UTF-16 units.
• The new build-pr.yml workflow and the workflow_dispatch trigger added to build-prerelease.yml.

docs/whatsnew/whatsnew-en-GB — only the version header changed. Production is still on 2.7.0 and CI deploys to the beta track, so the notes stay cumulative across that span. Nothing in v3.2.0 is user-visible, so no bullet was added. Measured at 434 of the 500 UTF-16 units Play allows, which leaves 66 units of headroom.

Does this close any currently open issues?

No.

Logs or Outputs

./gradlew test could not run in the preparation environment. The sandbox proxy returns 403 for dl.google.com, so Gradle cannot resolve the Android Gradle plugin, KSP, or the Firebase plugins, and offline mode fails the same way with nothing cached:

Could not resolve com.android.tools.build:gradle:9.2.1.
  > Could not get resource 'https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/9.2.1/gradle-9.2.1.pom'.
     > Received status code 403 from server: Forbidden

The PR Build workflow added in the previous commit runs ./gradlew test, ./gradlew lint and ./gradlew assembleDebug on this pull request, where the dependencies resolve. Please confirm that run is green before merging.

Any other comments?

Merging to main triggers auto-bump.yml, which adds its own ci: bump version code to N (v3.2.0) commit. That is expected. Confirm afterwards that versionName is still 3.2.0 — if it changed, the Fastlane bump lane has regressed and is writing versionName again, which is the bug fixed in v3.1.2.

The release itself stays manual: trigger the App Release workflow from the Actions tab to build the AAB and upload to the Play Store beta track.

Test Device Configurations

Not applicable. No source, resource, or layout file changes in this pull request.

🤖 Generated with Claude Code

https://claude.ai/code/session_01B9xFNhJj878gACSrZ73pU9

---

Generated by Claude Code