Skip to content

chore(release): 1.5.2 - #19

Merged
vannt-dev merged 1 commit into
mainfrom
chore/release-1.5.2
Sep 1, 2026
Merged

chore(release): 1.5.2#19
vannt-dev merged 1 commit into
mainfrom
chore/release-1.5.2

Conversation

@vannt-dev

Copy link
Copy Markdown
Owner

Cuts 1.5.2 from the four changes merged in #16, #17 and #18. 1.5.1+81.5.2+9, matching the one-per-release build-number convention.

What ships

  • Facebook reels and share links, which had stopped working entirely. Facebook began answering 400 to a page request that claimed a browser User-Agent without the Sec-Fetch-* headers a navigation carries, so /reel/, /share/r/ and /share/p/ were refused before the redirect could happen. The same fix restores Instagram's embed-player strategy, which had been served a payload-free page for the same reason.
  • A post gated as 18+ now says so, instead of pointing the reader at a visibility setting that was never the problem.
  • A share link no longer downloads its destination page twice — roughly 64 KB and 0.8 s per link.

The live-smoke work in #18 carries no changelog entry, per the repo's convention for test-only commits.

Release preflight

PR CI never exercises the release path — Detect version release and Publish release are gated on refs/heads/main and show as skipping here. So the workflow's own three gates were run locally first:

  • [1.5.2] section exists with non-empty notes, under the workflow's exact awkok
  • no v1.5.2 tag on origin yet — ok
  • 1.5.2 sorts above 1.5.1 from the current mainok

Plus flutter test 222 pass / 8 skipped, flutter analyze clean, node --test 7/7.

One judgement call worth flagging

This release contains a commit typed feat (the age-gate message), and strict semver would read a new user-facing behaviour as a minor bump — 1.6.0 rather than 1.5.2. I have gone with 1.5.2 as requested; it is defensible, since that change is arguably a correction to a misleading message rather than a new capability. Say the word and I will re-cut it as 1.6.0 before this merges.

Merging this to main triggers the automatic tag, signed APK, Web archive and GitHub Release.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RjyfcAcWuaNcXTc4ZdTofM

Facebook reels and share links, which had stopped working entirely.

- Facebook began answering 400 to a page request that claimed a browser
  User-Agent without the Sec-Fetch headers a navigation carries, which
  killed every reel and share link before any parsing could start. The
  same fix restores Instagram's embed-player strategy.
- A post Facebook gates as 18+ now says so, instead of telling the reader
  to check a visibility setting that was never the problem.
- A share link no longer downloads the page it points at twice.
@vannt-dev
vannt-dev merged commit 7580a40 into main Sep 1, 2026
7 checks passed
@vannt-dev
vannt-dev deleted the chore/release-1.5.2 branch September 1, 2026 02:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant