Move the build orchestrator to the Fallout stable channel (10.4.0) - #4
Open
lahma wants to merge 1 commit into
Open
Move the build orchestrator to the Fallout stable channel (10.4.0)#4lahma wants to merge 1 commit into
lahma wants to merge 1 commit into
Conversation
Fallout v10.4.0 is the first stable-channel release; the previously pinned 11.0.18 belongs to the edge channel. The stable CLI ships as Fallout.GlobalTool (the fallout command is unchanged), and Fallout.Common 10.4.0 resolves the patched System.Security.Cryptography.Xml 10.0.10 on its own, so the manual transitive pin is no longer needed (Fallout-build/Fallout#618). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
|
lahma
marked this pull request as ready for review
August 8, 2026 12:45
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
2 participants
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.
Fallout published v10.4.0, its first stable-channel release under the new dual-pace model. The 11.0.x line this repo pinned is the edge channel; 10.4.0 is newer (2026-08-07) and a feature superset despite the lower number (future stable releases move to CalVer, so the version line jumps ahead again).
Changes:
Fallout.Common11.0.18 → 10.4.0 inbuild/_build.csprojSystem.Security.Cryptography.Xml10.0.10 transitive pin — 10.4.0 resolves the patched version itself (Migrating against 10.3.49 produces a repo that fails restore with NU1903 (resolved by 10.4.0 GA) Fallout-build/Fallout#618). Restore verified clean of NU19xx.fallout.cli(edge-channel id, has no 10.4.0) toFallout.GlobalTool10.4.0 — the stable-channel tool id per Global tool package ID rename stranded 10.3.x consumers on Fallout.GlobalTool with no upgrade path Fallout-build/Fallout#575. Thefalloutcommand name is unchanged, sobuild.ps1/build.sh/CI need no changes.Same change as AngleSharp/AngleSharp.Js#138, minus the
.gitignorefix that repo needed — this repo's Python section already uses the narrowbuild/bin/build/objpatterns rather than a barebuild, so new files under the build project directory were never hidden (verified with a probe file).Verification:
dotnet build build/_build.csprojrestores clean and builds with 0 warnings; the restored graph resolvesFallout.Common 10.4.0and pullsSystem.Security.Cryptography.Xml 10.0.10transitively. A forced restore withNuGetAuditMode=all/NuGetAuditLevel=lowreports no NU19xx (audit confirmed live against a known-vulnerable control package)../build.ps1 Compileruns end to end:dotnet tool restoreresolves Fallout.GlobalTool 10.4.0, and Fallout Execution Engine 10.4.0.15 drives Restore + Compile to success acrossnet8.0andnet10.0with 0 warnings. Publish targets intentionally not run.🤖 Generated with Claude Code