Skip to content

DEPS-STABLE: Update shared FSharp.Core baseline and publish the coherent supplier #5253

Closed

Description

@EHotwagner

Parent Outcome: #5251
Work level: Delivery · Track: Active delivery · Intended Status: Done

Owner

Programme/root assigns the shared build-config producer owner and independent
reviewer. Consumer owners retain their own source and qualification acceptance.

Done when

Under the latest dependency-update request and Root's narrow supersession of
SDK-PATCH-01 Q3, upgrade the ordinary .github root and canonical shared
FSharp.Core pins from 10.1.401 to current listed stable 10.1.403. Refresh registry
facts at execution. Regenerate only affected active locks using actual cold
restores and preserve NuGet source determinism. Retain frozen SDK, release,
profile and historical evidence identities unless separately re-qualified.

Pass meaningful producer compiler/tests, existing Kit payload/materialization and
cold-lock source-exclusion controls, independent exact-head review and required
CI. Land through one normal producer PR, then publish the next unused coherent
Kit/Drivers/CLI set through the canonical release route and verify both feeds.
Record the exact supplier version and receiver owners for SDD, Governance,
Rendering and Game. Governance adoption must pair FCS 43.12.403 with Core
10.1.403. Each receiver retains separate source/qualification acceptance; this
producer Delivery cannot claim installed fleet adoption from its source merge.

Current deliverable

Shared source c914942 and coherent0.114.4 publication are accepted. Canonical forward41504251592 completed all16 durable effects, both feeds and promoted release431788123. Registry PR#5260 merged07229d66; all40 original PR runs succeeded and original merged-main feed41509055725 confirms every package-version matches both feeds.

Exact supplier: Kit/Drivers/Coord.Cli0.114.4, FSharp.Core10.1.403. Receiver ownership: SDD sdd1164_impl under FS.GG.SDD#1156/#1164; Governance governance_deps under FS.GG.Governance#484 (FCS43.12.403 paired with Core10.1.403); Rendering shared_deps5254 under FS.GG.Rendering#1507; Game algo_deps37 under FS.GG.Game#819, with Root retaining feature-owner overlap/integration coordination. No installed fleet adoption is inferred. Rendering's native source-preparation admission does not assert protected board enrollment.

Next action

Producer acceptance is complete. Receiver owners qualify their actual source and installed use independently; parent#5251 retains all-repository completion and final census.

Blocked on

No remaining publication or registry/feed blocker. Receiver qualification is explicitly separate and remains assigned in SDD#1156/#1164, Governance#484, Rendering#1507 and Game#819.

Acceptance evidence

Core source: #5253 (comment). Combined external source: #5254 (comment). Candidate41491677490/preflight41493838741 and completed publisher41504251592 bind original archive SHA25660ec3509a31829b1640533ff667841c28f5986c4ab3d1ec73a63c1d97ff217e7, content ID sha256:a20c568e191ec82ee430f3c9145b4466fa32ee17cd3b582176754cb441fb8e1e. Final journal generation33/all16verified; actual public package non-signature payloads independently match CLI87/Kit47/Drivers628 original leaves. Local org-feed403 remains scoped Unknown; protected publisher/journal/manifest verification supplies org-feed evidence. Original failed/checkpoint effects and forward admissions remain retained without reset/repack/resend. Registry PR: #5260; merged-main feed: https://github.com/FS-GG/.github/actions/runs/41509055725.

Reconciler installed-runtime82-file comparison, narrow immutable-original recovery and first fresh three-write apply accepted separately under#5206. No savings or full fleet acceptance claim.

Activity

  1. EHotwagner commented on Nov 2, 2026

    @EHotwagner
    ContributorAuthor

    Root admits source preparation for this Delivery pending batch enrollment. Owner: algo_deps37, retaining the complete producer promise through Root integration and the separately prepared canonical publication/readback. Intended Work level Delivery, Track Active delivery, Status In progress. Native parent #5251 is verified.

    The user's newer all-repository stable-dependency request supersedes SDK-PATCH-01 Q3 only for ordinary active FSharp.Core compatibility updates. Preserve actual frozen/digest-bound release, runtime-profile and historical identities. Use one isolated branch; hold opening a new .github PR until existing integration capacity clears. Coordinate source/version/projection overlap with existing #5241/#5250 owners; select a coherent version from actual release state at that boundary. No manual managed-consumer edits or feed publication is authorized by this source-preparation dispatch alone. Ordinary source verification budget 2 CPU / 3 GiB with fresh private outputs and read-only use of existing SDK installations.

  2. EHotwagner commented on Nov 2, 2026

    @EHotwagner
    ContributorAuthor

    Root source integration accepted: PR5255 exact5f490e02f1784055d9b50b0ada93105594be8b55 merged at15:34:28Z as1d9e00b947ad0d0d683e5bc69fc2c73e5fcd5d59. All major first-attempt repaired workflows passed (skill-quality, coordination engine, telemetry package, workspace) and required10/10. Deliveredtree d2159a3cfcd6a521466af30a8d75734751b2e06a equals exact reviewed source and tested synthetic merge. Normal guardedapply: boardlinked, transitionnoop, attempts1. The initial apply was refused before send due two owning Refs; removing only the secondary structuredRefs5228 preserved its attribution and ten-run promise, then current metadata checks passed. Publication and actual downstream acceptance remain open. Next coherent release composes5254 and the actual automatic-reconciler provider-schema repair5206; no premature stable-channel promotion.

  3. EHotwagner commented on Nov 2, 2026

    @EHotwagner
    ContributorAuthor

    Coherent0.114.4 publication is partial, with its original artifacts and journal preserved. Candidate41491677490/artifact13166040055 and preflight41493838741 passed on held source c914942cd0094179e07f12f0a2971f7daf059ff4. Original publisher 41495265202 failed during draft observation: its release-list population was malformed or duplicated. The report records draft dispatch applied; it does not establish completed publication.

    Independent fresh readback finds the exact tag at the selected source and one exact draft release431788123, with the original candidate marker and no assets. Protected journal generation4 retains tag=verified and draft=intent. The original transient population defect is not reproduced by the fresh complete121-release read. No failed run is relabeled successful and no package/promotion completion is claimed.

    Root separately admitted ordinary forward run 41497634725, using the same source, original archive digest, candidate and journal. The inherited draft intent is readback-only under the maintained fence; no tag/draft resend, journal reset or repack is authorized. Following effects retain their normal fresh guards. Main remains held; registry reconciliation, installed adoption and #5206/#5136 activation remain pending full publication/readback.

  4. EHotwagner commented on Nov 2, 2026

    @EHotwagner
    ContributorAuthor

    Ordinary forward publication 41497634725 completed its bounded observation window with disposition checkpoint, publicationComplete=false, and no reported failure. It verified the existing draft without resending it, all three GitHub packages and the public CLI. Generation 14 retains the original NuGet Kit intent after an acknowledged upload; its finite 135-probe visibility window expired. Root independently matched all 87 non-signature public CLI payload leaves to the original candidate, while a fresh Kit GET at 18:28:50 UTC returned 404. The draft still has no assets and is not promoted.

    The original archive, journal and held source c914942 remain unchanged. No package resend or new publisher has been admitted. Same owner observes only the pending Kit visibility through 18:40 UTC; a matching public payload will permit consideration of a separately admitted ordinary forward operation. Registry flip, installation and automatic board writes remain held. Original failure 41495265202 and this incomplete checkpoint are retained.

  5. EHotwagner commented on Nov 2, 2026

    @EHotwagner
    ContributorAuthor

    Root admitted ordinary forward 41501443662 after independently matching the now-visible public Kit payload to original candidate bytes and rereading held main c914942, original generation-14 journal (physical 06f2eb3f, state SHA e75f2d2d) and exact draft 431788123. The same archive 60ec3509 and candidate 41491677490/artifact 13166040055 remain bound. Inherited Kit intent permits readback settlement only; later absent effects retain normal admission. No package resend, repack or journal reset.

    An initial dispatch using the full commit as workflow ref was explicitly refused with HTTP 422 “No ref found”; no run was created. Fresh source/journal/run checks preceded one successful dispatch using supported main, still pinned to c914942. That refusal and all original publication history are retained. Registry and installation stay held until actual complete publication.

  6. EHotwagner commented on Nov 2, 2026

    @EHotwagner
    ContributorAuthor

    Forward 41501443662 retained a real main journal moved before CAS PATCH refusal while settling the already uploaded Drivers release asset. All six feed effects are verified. Independent readback matches all three native package-asset digests and downloaded archive bytes to the original candidate. The release journal remains generation 22, logical head 41b7a2d, state SHA 47942969; intervening Authority commits touch an ordinary-v2 shard, with writer identity unknown. No release-state change or package resend is inferred.

    After fresh original-journal, asset, held-main and active-run checks, Root admitted ordinary forward 41504251592 using the same candidate 41491677490/artifact 13166040055/archive 60ec3509/source c914942. It may settle the inherited Drivers asset intent by readback and complete remaining qualification assets, channel, manifest and promotion under normal guards. All prior runs and refusals are retained; no journal reset, repack or package replay. Registry and installation remain held pending actual complete publication.

  7. EHotwagner commented on Nov 2, 2026

    @EHotwagner
    ContributorAuthor

    Root accepts the complete producer scope of #5253. Reviewed source PR#5258 merged c914942; registry PR#5260 merged07229d66b02ca8569ad406f030f498d4084be6c4 with independent exact-head approval and all40 original CI runs successful. Canonical publisher41504251592 reports publicationComplete=true, generation33/all16 verified; release431788123 is promoted coherent-set/v0.114.4. Original merged-main feed41509055725 prints: “ok: every package-version equals the newest version live on the FS-GG feed and nuget.org.”

    Public CLI87/Kit47/Drivers628 non-signature payload leaves independently match the original candidate. Existing immutable archive, first failures, protected org-feed evidence and scoped local403 limitation are retained. Exact suppliers and all four receiver owners are recorded in the body. Receiver installation/qualification is separate and remains open; parent5251 is not accepted by this producer closure. No token/cost/speed savings claimed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions