Skip to content

Say what ran on x86_64 in the 7.1.5.5 and 6.1.6.5 notes - #28

Merged
sbokatuk merged 1 commit into
mainfrom
correct-x86-64-release-notes
Oct 30, 2026
Merged

sbokatuk merged 1 commit into
mainfrom
correct-x86-64-release-notes

Conversation

@sbokatuk

Copy link
Copy Markdown
Owner

Both notes said x86_64 was not run on a device. That was true when they shipped, but CI runs added since have covered it, so the notes now understate what was tested.

This changes only those lines, and the merge doesn't release anything: auto-release.yml ignores edited notes (--diff-filter=A).

What changes

  • 7.1.5.5.md and 6.1.6.5.md, last line: says which variants ran on x86_64 after the release, and which five didn't.
  • 7.1.5.5.md, line 17: the claim that Audio carries the RELRO defect on x86_64 is now backed by a real failure of published 7.1.5.4.
  • 6.1.6.5.md, line 17: left alone. 6.1.6.4 never ran on x86_64, so "Nor was x86_64" is still accurate there.

Evidence

All of it is from the x86_64 emulator logs.

Run What ran Result
41077313167 Audio, Video on net8.0-android34.0, API 31 and 35, FFmpegKit 7.1.7 and 6.0.4 passed=15 failed=0, ffmpeg=n7.1.5 / ffmpeg=n6.1.6 on all 8 legs
Same run The example app (Full) on net10.0-android36.0, API 35, both tracks One conversion, sample run passed
41066224566 Published 7.1.5.4 Audio on net8.0-android34.0, API 31 can't enable GNU RELRO, passed=1 failed=14

The first two rows are -beta builds of the same FFmpegKit libraries, not the published packages. The notes say so.

Already applied

The same lines are live on the 7.1.5.5 and 6.1.6.5 GitHub Releases, as the maintainer approved. Nothing else in those releases changed, and Latest stays on v8.1.3.1: the edit passed --latest=false, because GitHub gives the label to the newest release otherwise (see #26).

If the wording changes in review, those two releases need the same edit.

Not covered

Min, MinGpl, Https, HttpsGpl and FullGpl have still not run on x86_64 on these tracks. Both notes say so.

🤖 Generated with Claude Code

Both notes said x86_64 was not run on a device. That was true when they
shipped, but the CI runs added afterwards covered Audio, Video and Full
on the same FFmpegKit libraries, and published 7.1.5.4 Audio was seen
failing with the RELRO error on x86_64.

6.1.6.4 itself never ran on x86_64, so that note's sentence about the old
package stays.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings October 30, 2026 16:48

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are identified for the documentation-only updates describing post-release x86_64 testing in two older-track release notes.

No open issues 🎉

What changed in this PR

Updates two older-track release notes to reflect post-release x86_64 emulator testing. These are documentation-only changes; no new release is triggered.

Changes:

  • Records successful Audio and Video device checks and a Full example-app conversion using later builds of the same native libraries.
  • Preserves the distinction from testing the published packages and identifies the five variants still untested on x86_64.
  • Documents the observed GNU RELRO failure in published 7.1.5.4 Audio.
File Description
docs/​release-notes/​7.1.5.5.md Adds post-release x86_64 coverage and confirms the earlier Audio RELRO failure.
docs/​release-notes/​6.1.6.5.md Adds post-release x86_64 coverage while preserving the earlier release’s testing limits.

Review effort: Balanced

@sbokatuk
sbokatuk merged commit e1b8cba into main Oct 30, 2026
18 checks passed
@sbokatuk
sbokatuk deleted the correct-x86-64-release-notes branch October 30, 2026 17:44

This branch was successfully deployed

1 active deployment
nuget.org — 56e2f11a Deployed Oct 30, 2026 by sbokatuk via publish beta to nuget.org #40
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.

3 participants