Repository navigation
Release v0.4.0-alpha.4
Pre-release
Pre-release
·
563 commits
to main
since this release
Added
morphirup, the standalone Native AOT toolchain manager, first slice:morphirup --version, plan-onlymorphirup setup --planandmorphirup doctorover local files. It needs neither .NET, ICU nor OpenSSL: it runs in invariant globalization mode, normalizes to NFC with its own Unicode 17.0.0 tables and computes SHA-256 with BouncyCastle's managed implementation. Setup resolves a.morphir/toolchain.tomlrequest against a recipe file for every platform the lock would record and prints the plan with itsplanSha256. The plan carries the complete lock setup would write, so the digest pins every platform's closure and the request's exact bytes;--expect-planrefuses another plan withplan_changed.--repository-idis copied into the plan and lock as given and not checked, and the plan's sources are labels, not verified provenance. Without--request, the project request is discovered from the start directory up to the discovery boundary, by default the root of the file system; discovery stops at a.morphir/toolchain.tomlin any form, and anything there that is not a readable regular file isdocument_unavailable. Doctor reads the lock beside the request it found or was given, and checks that the lock binds the request bytes, records the current platform and, with--recipeand--repository-id, names that repository (repository_mismatch) and is a closure the recipe allows. A request whose bytes differ from the locked ones only by CRLF line endings or a byte order mark isrequest_changednaming that cause.setup --plananddoctorwrite one manager result document to stdout. Files are read only when they are regular files, up to 1 MiB for a request, lock or sizes file and 16 MiB for a recipe, with five seconds to open and thirty seconds for each read; read errors are reported inmorphirup's own words, and a request, lock or recipe that cannot be read isdocument_unavailable. A document nested deeper than 64 levels isinvalid_document. Acquisition, installation and activation are not implemented. Exit code 2 means the command was not run, for example an unknown option, a missing--recipeor--repository-id, an invalid option value, a machine that is not one of the eight platforms, or an artifact with no size in--artifact-sizes; it writes nothing to stdout. Provisional:--project,--boundary,--recipe,--repository-id,--recipe-target,--artifact-sizes,--requestand--lock; the file bounds; the version bound (256 characters, 15 digits per numeric identifier, refused asinvalid_value); and exit code 3 (internal error), which writes nothing to stdout (#558)- Releases attach
morphirupforlinux-x64,linux-arm64,win-x64andosx-arm64: the executablemorphirup-<rid>(morphirup-win-x64.exeon Windows), the archivemorphirup-<rid>-v<version>.tar.gzwith the executable,LICENSE,NOTICEandTHIRD-PARTY-NOTICES.txtunder<rid>/, the same notices asmorphirup-v<version>-THIRD-PARTY-NOTICES.txt, and the checksum filemorphirup-v<version>.sha256insha256sum -cformat. The notices are generated from the assemblies the Native AOT compiler linked, with each package's license and notice files; the build fails when a linked package has no license text. The release job builds each with Native AOT on a runner of its platform and runs the published file, not a source build, from a folder whose path has a space, withPATHreduced to the system folders and noDOTNET_*variable: it must print the release version and make a plan-only setup with the recorded plan digest. The Linux executables are linked inubuntu:22.04, pinned by digest, so they need glibc 2.35 or later (Ubuntu 22.04, Debian 12 or later); the release job fails if one needs a newer glibc version, and runs each indebian:12-slimandubuntu:22.04(with itslibssl3package removed), with no .NET,libicu,libsslorlibcrypto. A Linux executable needs nothing else from the machine. They do not run on musl distributions such as Alpine. Nothing else is checked. The files are not code-signed and the macOS file is not notarized, so Gatekeeper can refuse a copy that a browser downloaded until its quarantine attribute is removed; this was not checked on a Mac. The release does not download, install, update or activate a toolchain and does not verify signed metadata. The pull request workflowmorphirupruns the same build and check on all four platforms (#558) Morphir.Toolchain: readers and writers for the0.1.0-draft.1toolset recipe, project toolchain request, portable lock, installation receipt and manager result of finos/morphir, with pure resolution, lock, plan and project discovery functions, pinned to finos/morphir1451c081f. A provider'sprotocolVersionis a MEP version on the supported 0.2 line (every prerelease of0.2.0and every final0.2.x); MEP0.1is refused, and an external provider carries onemodelTupleand nomodelInputormodelOutput. Plan digests and target paths are normalized to NFC with the library's own Unicode 17.0.0 tables, generated byscripts/generate-nfc-tables.fsxand checked against all ofNormalizationTest.txt, so neither depends on the machine's ICU. It runs every case of the pinned finos/morphir contract manifests that is a pure function of documents and authenticated metadata. The cases that need a TUF client to verify metadata, or the installation work of later slices, are skipped by name with their reason (#558)- The F# frontend extension
morphir-fsharp-frontendhas a self-contained process delivery: a folder with the guest, the F# compiler service and its own .NET runtime, published with theSelfContainedProcessprofile or the build targetPublishFSharpFrontendProcess --rid <rid>, which also writes a zip or.tar.gzarchive (files at the root, ordinal order, fixed time stamp and modes) and keeps the publish's lock file beside it. A host such as the nativemorphirstarts it with--extension. Checked on Windows ARM64 only, in an environment that hides the machine's .NET (nodotnetonPATH, noDOTNET_*variables, an empty NuGet folder and no global install): the automated test runs the guest there, and the nativemorphircompiled F# through it there by hand. It was not run on a machine with no .NET at all. Releases do not publish it yet. The framework-dependent dotnet tool is unchanged morphir-fsharp-backend: the F# generator as a MEP0.2.0-draft.1guest, packaged as the framework-dependent dotnet toolMorphir.CodeGeneration.FSharp.Extensionwith the extension idorg.finos.morphir.fsharp-backend. It servesmorphir.backend.generateModelfor the targetfsharpwith JSON model tuples for IR4.0.0and3.0.0, for hosts that have no built-in F# backend. The built-inmorphir.fsharpstays the backend ofmorphir generate, which does not start the extension. Releases publish the package next toMorphir.ToolMorphir.Mepbackend messages: the pinnedgenerateModelrequest, generate result and artifact types, andGenerateModel.admit, the guest check of a request. Compatibility note for F# code that opensMorphir.Mep: like the other wire types, the new recordsGenerateModelRequest,GenerateResult,ArtifactandAdmittedGenerateRequestare at the top level of the namespace, and their labels (Model,Input,Target,Options,Path,Content,Binary,Success,Artifacts,Diagnostics,Request,Guarantees) can change which record type F# infers for an unannotated record expression or member access. Annotate the record type where that happens. The type nameArtifactalso exists asMorphir.Conformance.Artifact; qualify it when both namespaces are openMorphirApplicationinMorphir.Tooling: the shared command layer (the scenarios,infoand--version) that every entry point runs.Morphir.Program.RunandMorphir.Program.CreateAppkeep their signatures and delegate to it- A managed
morphirentry point (src/Morphir.Managed) and the managed composition it shares withdotnet-morphir(src/Morphir.Tooling.Managed), which holds the in-process F# frontend. It is not packaged or released yet - Build: named release profiles for the four .NET deployment offerings.
PublishReleaseandPackReleasewith--deployment native-aot|self-contained|framework-dependent|dotnet-tooland--ridproduceartifacts/release/morphir-dotnet-<release>-<deployment>-<rid>.<zip|tar.gz>(orMorphir.Tool.<release>.nupkg) with a build-side.build-launch.jsonbeside it, for win-x64, win-arm64, osx-x64, osx-arm64, linux-x64 and linux-arm64. The managed profiles are untrimmed folders with the in-process F# frontend. The same publish folder always gives the same archive bytes (fixed time stamp, ordinal entry order, mode 0755 for the launch file andcreatedump, 0644 otherwise).PackReleasefails when the publish folder contradicts the launch metadata, and checks the tool package asPackTooldoes. A release with build metadata (1.2.3+abc) is refused. Releases do not publish these archives yet, and no platform is qualified yet (#558)
Changed
dotnet-morphirruns the shared command layer with the managed composition and no longer references the AOT-compatiblemorphirproject, so the tool package no longer containsmorphir.dll. Its commands and its F# frontend are unchanged- Build:
PublishExecutable,PublishSingleFileandPublishSingleFileUntrimmedtake their settings from the release profile model.PublishSingleFilekeeps the settings and names of the legacy release assetsmorphir-<rid>[.exe]andmorphir-<rid>-v<version>.tar.gz.PublishExecutablenow leaves out debug symbols and documentation files, and findsmorphir(notMorphir) on Linux and macOS. Size figures ofPublishExecutableoutput from before this change included the symbol file, so they are not directly comparable with new figures (#558) - Build: publishes for one runtime identifier write their NuGet lock files under
obj/publish-lock/<rid>/(theMorphirRidSpecificPublishproperty), so they no longer add RID sections to the committedpackages.lock.jsonfiles (#558) - Build:
src/Morphir.Managedfails to build withPublishAotorPublishTrimmed, and a project whose references resolve two differentmorphir.dllassemblies (src/Morphirandsrc/Morphir.Managed) fails to build just publish-executable,just publish-single-fileandjust publish-single-file-untrimmedrun the Nuke targets; theirVERSIONargument is gone, as the version comes fromCHANGELOG.md.scripts/measure-compile-aot.shpublishes with the native-aot profile's settings
Removed
scripts/publish-single-file.csandscripts/publish-single-file-untrimmed.cs, which called a removedcodegen writecommand. Use thePublishSingleFileandPublishSingleFileUntrimmedtargets (#558)
Fixed
- The F# frontend takes its framework references from the framework's runtime assembly list, so in a self-contained folder it no longer gives the compiler the application's own assemblies (
Morphir.*, the compiler service). The references of the dotnet tool and the in-process frontend are unchanged. It reads the deps files that the host lists (APP_CONTEXT_DEPS_FILES, joined with;on every platform). When it cannot give the compiler its references (no file location, a self-contained folder without a framework list, no trusted platform assemblies, or a listed deps file that cannot be read), compilation fails with onefsharp.references_unavailableerror instead of an exception Morphir.Myriad.SystemTextJsonbuild targets: an absoluteIntermediateOutputPath(for example with--artifacts-path) no longer gives an invalid output folder for the generated JSON contexts