chore(release): 1.5.2 - #19
Merged
Merged
Conversation
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.
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.
Cuts 1.5.2 from the four changes merged in #16, #17 and #18.
1.5.1+8→1.5.2+9, matching the one-per-release build-number convention.What ships
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.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 releaseandPublish releaseare gated onrefs/heads/mainand show asskippinghere. So the workflow's own three gates were run locally first:[1.5.2]section exists with non-empty notes, under the workflow's exactawk— okv1.5.2tag on origin yet — ok1.5.2sorts above1.5.1from the currentmain— okPlus
flutter test222 pass / 8 skipped,flutter analyzeclean,node --test7/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.0rather than1.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
maintriggers the automatic tag, signed APK, Web archive and GitHub Release.🤖 Generated with Claude Code
https://claude.ai/code/session_01RjyfcAcWuaNcXTc4ZdTofM