Repository navigation
Release v0.5.0-alpha.1
Pre-release
Pre-release
·
62 commits
to main
since this release
Added
- Documentation: a getting-started walkthrough, Your first model with morphirup, and a troubleshooting page. The walkthrough installs
morphirup, sets up the toolchain, compiles theexamples/morphirup-fsharpmodel, generates F#, changes a rule and compares the output, then compiles and generates again offline. The getting-started pages now cover tasks only: the local candidate journey moves to the contributing section, implementation detail moves to the reference pages, and troubleshooting moves to the new page. The morphirup reference opens with a task section forsetup,show,selectandrun, andexamples/morphirup-fsharp/README.mdrepeats the walkthrough's commands. - Install
morphirupwith one command.scripts/install-morphirup.sh(POSIXsh, Linux x64 and ARM64, macOS on Apple silicon) andscripts/install-morphirup.ps1(Windows x64 and ARM64, Windows PowerShell 5.1 and PowerShell 7) install the newestfinos/morphir-dotnetrelease that hasmorphirupfor the machine, prereleases included, or the release given with--version/-Version. Each script checks the file against the release'smorphirup-v<version>.sha256and installs nothing on a mismatch or a missing line. Theshscript installs to~/.local/binand prints thePATHline to add; the PowerShell script installs to%LOCALAPPDATA%\Programs\morphirupand adds it to the userPATH. Intel macOS and musl Linux are refused. On restricted networks, both scripts useHTTPS_PROXYandNO_PROXY(the PowerShell script also uses the Windows proxy settings and the current user's proxy credentials, and passesHTTPS_PROXYitself on Windows PowerShell 5.1), accept an HTTPS mirror inMORPHIRUP_DOWNLOAD_URL, fall back to the release feed on github.com when api.github.com cannot be reached, and stop connecting after 30 seconds. The manually triggered workflowinstall-scripts.yml(inputsversionandplatforms) runs both scripts and the mise commandmise use -g 'github:finos/morphir-dotnet[matching=morphirup,version_prefix=v,prerelease=true]'(also with@<version>) on Linux, macOS and Windows. - Release setup on macOS ARM64: the release attaches the
osx-arm64toolchain (the self-contained host archive, the F# frontend and backend archives with their release and manifest files,morphir-host-candidate-osx-arm64.json,morphir-extensions-osx-arm64.jsonand the bundlemorphir-toolchain-osx-arm64.json), and its oneSHA256SUMScovers win-x64, win-arm64 and osx-arm64. On Apple silicon,morphirup setup --yes, thenrun -- compileandrun -- generate --target fsharp, work from the published release. The release job packs the toolchain on the native macOS ARM64 runner ofbuild-morphirupand runs the acquired setup journey there; the pull request workflow does not, so its macOS job is unchanged.WindowsToolchainChecksumstakes--toolchain-platformsfor a run that packs only some toolchains. - Experimental
morphirupsetup on macOS ARM64 (osx-arm64).morphirup setup --local-developerwith a local candidate, host archive and bundle, thenselect, thenrun -- compileandrun -- generate --target fsharp, works on Apple silicon with no .NET onPATHand no network. Release setup (setup --yes) accepts anosx-arm64manager and bundle too. Intel macOS stays unsupported. - Build:
PackWindowsToolchain --rid osx-arm64packs the macOS ARM64 setup inputs: tar.gz archives, the entry pointsmorphir,morphir-fsharp-frontendandmorphir-fsharp-backend, and the candidate, selection, release descriptors, manifests, bundle andSHA256SUMS. The target keeps its name, and the Windows outputs are unchanged. Morphir.Extensions.Installationinstalls tar.gz extension packages by the package policy of ZIP packages: at most 4096 entries (for tar, PAX/GNU metadata headers count too), only regular files and directories, the same package path rules (a./prefix, astar -C dir -czf package.tar.gz .writes, is removed), the same size bounds, no inspection of a resource as a nested archive, and the canonical modes 0555 and 0444. Before, it refused them withpackage.format_not_implemented. A package format other thanziportar.gzis refused withpackage.archive_formatbefore staging.
Changed
- The README and the installation guide start with
morphirup: the install scripts, mise, manual download with checksum verification, and what works on each platform: macOS on Apple silicon and Windows set up, compile and generate; on Linuxmorphirupinstalls, butmorphirup setupdoes not support Linux yet. Troubleshooting moves to its own page. The proto,install-*.shanddotnet tool installroutes to the standalonemorphirCLI follow under "Other ways to install the standalone morphir CLI". The duplicate pagedocs/content/getting-started/installation.mdis gone; its address redirects to the installation guide. - The composed local-toolchains family moves from
0.1.0-preview.3to0.1.0-preview.4(finos/morphir#1164, merged as648ae374; spec), for every platform. Preview.4 addsosx-arm64with the archive formattar-gzip. The producer writes preview.4, andmorphirupreads preview.4 only: candidates, bundles, receipts, selections and generations of preview.3 (written by 0.4.0-alpha.5 and earlier) are not read and are not converted.select,showandrunread only the preview.4 selection pointer: in a Home set up with preview.2 or preview.3 they refuse withlocal.setup_required, which says to runmorphirup setup --yesagain (and thenselect, for a local candidate). Setup in that Home installs preview.4 beside the earlier generations without reading them, and replaces the selection pointer. The historical preview.1 local route is unchanged. The candidate reader refuses anosx-arm64candidate that does not declaretar-gzip, and a Windows candidate that does not declarezip. Setup and run refuse anosx-arm64entry point that is notmorphirwithlocal.launch_structurewhen they check the archive or the installed folder. morphirupoff Windows uses the physical path of the parent folders of--home, with each link resolved (at most 40). The installed host refuses a source file below a link, and on macOS$TMPDIRis below the link/var. The last part is not followed, so a Home that is itself a link is still refused.morphirup runand the setup probes also removeDOTNET_ROOT_ARM64from the host's environment.- A refused
morphirup setup,selectorshowwrites a local-toolchains0.1.0-preview.4result, on the preview.1 local route too. Before, every refusal except the composed local setup's wrote the preview.1 result withorigin: local-developer. Theoriginis now the origin of the preview.4 generation thatselectnames or of the selection thatshowreads, andlocal-developerwhen there is none. A completed preview.1 step still writes the preview.1 result.
Fixed
morphir ir verifyno longer runs without end on a typical IR file. Each union branch of the schema checked its whole subtree even when the tag was another branch's, so the time grew exponentially with nesting. Thegreeting-example.jsonIR v3 example of finos/morphir (29 KB) ran for more than ten minutes and now takes under a second. The 3.5 MB LCR example takes about 20 seconds. A value with an unknown tag still lists the tags that were expected. For a value with a known tag, the deep errors of the other branches are gone: each other branch reports only that its tag does not match.morphir ir verifyaccepts IR v3 whose values carry their inferred types as attributes, as morphir-elm writes them, and names with a word that is a number. Both come from the current finos/morphir v3 schema. Before, the greeting example was not valid.morphir ir verifyreads IR nested up to 512 levels. Before, a file deeper than 64 levels, such as the LCR example of finos/morphir, was reported as malformed JSON.morphir(and somorphirup run -- compileandrun -- generate) no longer writes[INF] Foundatio.Mediator registered 3 handler(s) and 0 middleware.to stderr. The CLI logger caps theFoundatio.Mediatorcategory at Warning, so the mediator's warnings and errors are still shown. Stdout is unchanged.- Build: restoring the solution no longer rewrites the committed
packages.lock.jsonof theMorphir.Configuration.IO.SmokeandMorphir.Configuration.Microsoft.Smokehosts with the host's RID, so release artifacts built on Linux or Windows no longer record a dirty origin. A trimmed publish of these hosts passes-p:PublishTrimmed=true, and CI fails when restore changes the working tree. - On Linux and macOS, an extension installation lock is free as soon as its owner releases it. Before, the lock stayed held while another thread of the same process was starting a child process, because that child shared the lock's file until it ran its program. A second extension operation in that window could fail with "Lease is busy".
- Extension installation works on Linux ARM64. Before, every operation on the extension Home there failed with
Cannot access '…/.morphir': native error 22.: installing and registering extensions, reading the installed state, andmorphirupdownloads. The safe file layer passed the Linux x64 values ofO_DIRECTORYandO_NOFOLLOW, which on ARM64 meanO_DIRECTandO_LARGEFILE, so it also did not refuse a symbolic link there. It now takes its open flags from a table for Linux x64, Linux ARM64 and macOS.