Merge release/8.17 into main

[wpmobilebot]

Merging release/8.17 into main.

Via intermediate branch merge/release-8.17-into-main, to help fix conflicts if any:

                            release/8.17  ----o-- - - -
                                               \
            merge/release-8.17-into-main        `---.
                                                     \
                                    main  ------------x- - -

[dangermattic]

	1 Message
📖	This PR has the releases label: some checks will be skipped.

Generated by 🚫 Danger

[claude]

Claude finished @sztomek's task in 1m 22s —— View job

---

PR Review: Merge release/8.17 into main

• Read PR diff and commits
• Review CHANGELOG.md changes
• Review version.properties changes
• Post review feedback

This is a routine release-to-main merge-back. The only changes are CHANGELOG.md and version.properties, so there's no application code to assess for bugs, security, or performance. Feedback below focuses on the changelog content.

Findings

🟡 Duplicate changelog entry (needs attention)

In the 8.17 section, PR #5613 — "Resolve generated chapter seeks through on-demand audio fingerprinting" — is now listed twice:

• under New Features (CHANGELOG.md:20-21)
• under Updates (CHANGELOG.md:27-28)

This looks like a merge-conflict resolution artifact from bringing the release branch back into main. One copy should be removed. Since it's a follow-up refinement to existing fingerprinting work rather than a brand-new feature, keeping it under Updates and dropping the New Features copy is likely the more accurate categorization — but the release owner should confirm. I left an inline suggestion on the relevant lines.

Fix this →

✅ version.properties

versionName 8.17-rc-1 → 8.17-rc-2 and versionCode 9442 → 9443 — a consistent, monotonic bump. The change also adds the previously-missing trailing newline at end of file. 👍

Summary

The merge is fine to proceed; the only real item is the duplicated #5613 changelog line. It's cosmetic (release-notes only) and won't affect the build, but worth tidying before this lands on main so the 8.18 notes stay clean.

[claude]

Claude finished @sztomek's task in 32s —— View job

---

PR Review: Merge release/8.17 into main

• Read updated PR diff and commits
• Verify the previously-flagged duplicate changelog entry
• Review version.properties changes
• Post review feedback

This is a routine release-to-main merge-back. Only CHANGELOG.md and version.properties changed — no application code to assess for bugs, security, or performance.

Findings

✅ Duplicate changelog entry is now resolved

The earlier concern — PR #5613 ("Resolve generated chapter seeks through on-demand audio fingerprinting") appearing twice in the 8.17 section — has been fixed by this branch update. It now appears exactly once, under Updates (CHANGELOG.md:25-26), which matches the categorization suggested in the earlier review. The 8.17 section reads cleanly:

• New Features: [HLS] Integrate audio-only setting #5572, Add support for the Flightcast transcript format #5544, Add Listening Activity heatmap info button #5536, [HLS] Connect firebase flag #5602, [HLS] Offer option to switch to HLS stream when playing downloaded episodes #5620
• Updates: Play progressive video episodes as audio when audio only is enabled #5627, Tap into ExoPlayer's cache instead of a standalone MediaSource for fingerprinting #5618, Resolve generated chapter seeks through on-demand audio fingerprinting #5613
• Bug Fixes: fix: Respect the data warning when caching the entire playing episode #5567, Reduce the chance of episode playback progress reverting during listening history sync #5552, Catch seek exception in SimplePlayer to prevent playback crash #5550, Fix Automotive crash when Google Assistant connects to media session #5551, Fix podcast episode row button not switching to play when connected to Chromecast #5604

✅ version.properties

versionName 8.17-rc-1 → 8.17-rc-2 and versionCode 9442 → 9443 — consistent, monotonic bump, with the trailing newline at EOF now restored. 👍

Summary

The previously-flagged issue is resolved and no new concerns were found. The merge-back looks good to proceed. ✅