docs: 0.1.0-alpha.4's notes - 0.1.0-beta.37 on .NET 11.0.0, the last alpha for now; how its sync differs, owner-only item 35 (alpha.4 PR-1) (#382)

- docs/changelog/0.1.0-alpha.4.md: the experimental-build warning, why
  this alpha exists (to bring an installed alpha off the release
  candidate by an update), that the alphas pause after it, and what a
  paused alpha costs - no update, the anti-cheat list included; ten
  betas later an older alpha no longer finds it. Install the beta.
- CHANGELOG.md: its row.
- HANDOFF: the alpha.4 part of START HERE - every switch file conflicts
  this time and main's side is taken for each, leaving RELEASE_LINE -
  and owner-only item 35.

Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
poli0981andClaude Fable 5.2 authored and GitHub committed 2026-11-11 00:29:52 +00:00
1 parent 1a7fbf3ce7
commit 428b723bb3
3 files changed
+70

No files matched your search

+1
View File
@@ -41,6 +41,7 @@ Newest first. Each file holds that release's section exactly as it stood here.
| Version | Date | Notes |
|---|---|---|
| `0.1.0-alpha.4` | 2026-11-11 | [`docs/changelog/0.1.0-alpha.4.md`](docs/changelog/0.1.0-alpha.4.md) |
| `0.1.0-beta.37` | 2026-11-11 | [`docs/changelog/0.1.0-beta.37.md`](docs/changelog/0.1.0-beta.37.md) |
| `0.1.0-beta.36` | 2026-11-10 | [`docs/changelog/0.1.0-beta.36.md`](docs/changelog/0.1.0-beta.36.md) |
| `0.1.0-beta.35` | 2026-11-09 | [`docs/changelog/0.1.0-beta.35.md`](docs/changelog/0.1.0-beta.35.md) |
+27
View File
@@ -158,6 +158,25 @@ SonarScanner 12.0.0 on the 11.0 runtime; InspectCode 2026.2.3.1 and 2026.3.0 aga
**Owner-only:** item 34 — beta.37 on real hardware, a hooked session on .NET 11.0.0, and Windows 10 if a PC with it is
at hand.
### 0.1.0-alpha.4 — the fourth alpha, the same day, and the last for now (D98)
`alpha` takes main at this pull request — `v0.1.0-beta.37` and these notes, no other change — by a merge commit. **This
sync is not like the three before it**: main now holds what the switch held (`global.json`, the TFM, the three
packages, `legal/licenses/nuget/`, the *Transitive* row), so every switch file conflicts, and each is resolved by
taking main's — the branch's RC3 lines go, `RELEASE_LINE` stays `alpha`, and `git diff --name-only origin/main` on the
merged tree must print that one name. Its gate must pass on `alpha` before the pull request is merged by hand (the
branch has no auto-merge); the release runs from the signed tag `v0.1.0-alpha.4` on `alpha`, with its delta from
alpha.3. Its notes are `docs/changelog/0.1.0-alpha.4.md`: the warning, and that it is the last alpha for now.
- **After it the line rests** (`12_BUILD` §The alpha line): no sync follows a beta and no alpha is cut until a newer
.NET has a preview. `FlAlphaLineRests` in `Directory.Build.props` says so to the build; the next trial sets it to
`false` on `alpha` with the rest of the switch.
- **What a resting alpha costs its user** is in its notes, the guide and its banner: no update, the anti-cheat list
included; and once ten betas have followed it, a copy of alpha.3 or older no longer finds alpha.4 (Velopack reads
the newest ten releases).
**Owner-only:** item 35 — the fourth alpha on real hardware, and the beta installed over it.
## Owner-only — no PR can close these
@@ -423,6 +442,14 @@ at hand.
three alpha strings that changed or are new (`Alpha_Banner_Body_Format`, `Alpha_Banner_Body_Resting_Format`,
`About_Runtime_Alpha_Format`) and of the first-run summary's first line. (f) **Going back** — only if something is
wrong: install beta.36 over it; the ledger opens.
35. **alpha.4 on real hardware — the last alpha for now** (D98). (a) **The update from alpha.3**: Help ▸ Check for
updates offers alpha.4 and *Restart to update* installs it — a large download, the runtime moving from the release
candidate to 11.0.0. (b) The terms window shows the **EULA 1.7, the Disclaimer 2.14 and the Alpha notice 1.1** and
waits for the notice's box; `…\backups\ledger-before-0.1.0-alpha.4.db` exists beside the older copies, and opens;
the ledger stays at schema 22. (c) **The banner says the alpha line is paused** and to install the beta — not the
experimental-build warning — and Help ▸ About reads *Alpha build — runs on .NET 11.0.0*, with no "prerelease".
(d) **Then install beta.37 over it**: the installer asks to replace it; the beta opens the ledger, shows no Alpha
notice, and its update channel is no longer locked.
**Answered 2026-08-05, do not re-ask:** remove `gameguard` and keep `guard` (approved
over a red `Rules` gate, with the reasoning recorded in the merge commit); vendor NVAPI
headers **and** `amd64/nvapi64.lib`; Windows 11 is the **measurement scope** only —
+42
View File
@@ -0,0 +1,42 @@
<!-- The fourth alpha's notes (D73, D98), on main as every release's are; the alpha branch takes them with its sync. CHANGELOG.md lists every release. -->
## [0.1.0-alpha.4] - 2026-11-11
> ⚠ **EXPERIMENTAL BUILD — YOU USE IT AT YOUR OWN RISK — AND THE LAST ALPHA FOR NOW.** This is an **alpha**: the source
> of `0.1.0-beta.37` built on **.NET 11.0.0**, Microsoft's final release of .NET 11 (SDK `11.0.100`) — the same .NET the
> betas run on from `0.1.0-beta.37`. It exists to bring an installed alpha off the release candidate. **After it the
> alphas pause**, and a paused alpha gets no update — the list of anti-cheat software FrameLedger refuses included.
> **Install the latest beta over it.** Before it runs it shows the *Alpha notice* (`legal/ALPHA_NOTICE.md` 1.1), which
> you must accept, with its own box to tick.
**The fourth alpha: `0.1.0-beta.37` on .NET 11.0.0.** The alphas were made to try .NET 11 before the betas relied on it.
.NET 11 shipped on 10 November 2026 and the betas moved to it the next day (the beta's notes,
`docs/changelog/0.1.0-beta.37.md`), so an alpha and a beta now differ in nothing but what an alpha adds for itself. This
one is published so that a copy of `0.1.0-alpha.3`, which runs on a release candidate Microsoft no longer supports,
reaches the finished .NET 11 by an update — an alpha never updates to a beta.
**Then install the beta.** No alpha will follow until there is a newer .NET to try (.NET 12's first previews, expected
in 2027). Until then this build stands still: no fixes, and **its anti-cheat list is the one it shipped with**, because
that list reaches FrameLedger only inside an update. Its banner says so each time it starts. Download the newest beta's
`FrameLedger.App-win-Setup.exe`, verify its hash against that release's `SHA256SUMS.txt`, and let it replace the alpha;
your database stays where it is, and the beta opens it. What an alpha is and how to go back: the user guide's *Alpha
builds* page (`guide/11-alpha-builds.md`), and the *Alpha builds* section of `LIMITATIONS.md`.
**Updating from `0.1.0-alpha.3`:** Help ▸ Check for updates, then *Restart to update* with no game running. Before it
first opens your database it copies it to `%LOCALAPPDATA%\FrameLedger\backups\ledger-before-0.1.0-alpha.4.db` (the
newest three copies are kept). The terms window shows the **EULA 1.7**, the **Disclaimer 2.14** and the **Alpha notice
1.1**, and waits for the notice's box to be ticked. The ledger stays at schema 22 and the detection rules at
`2026.11.2`. The download is large, because the .NET runtime inside the package is replaced whole. **One limit:**
FrameLedger's updater looks at the newest ten releases, so once ten betas have been published after this alpha, an
older alpha no longer finds it — install the beta by hand then, as above.
**Windows and your PC:** as for the beta from `0.1.0-beta.37` — Microsoft supports .NET 11 on Windows 11, and on Windows
10 only in its LTSC and IoT editions; FrameLedger is untested and unsupported on Windows 10 22H2; a processor without
SSE4.2 and POPCNT cannot start it.
### What differs from 0.1.0-beta.37
Nothing in the runtime, the compiler or the libraries: both are built on .NET 11.0.0 from the same source, and the part
of FrameLedger loaded into a game is the beta's. What an alpha adds is its own: the Alpha notice in the terms window, the
ALPHA badge and the banner — which in this build says that the alphas are paused — the locked update channel, and the
copy of the database before it is first opened.