Releases: MagnusOpera/terrabuild
Releases · MagnusOpera/terrabuild
0.193.0-next
- Add explicit extension dependency resolution metadata (
PathorScope) so scripts can declare whether dependency identifiers resolve by workspace path or extension scope, keeping canonical project IDs stable for pnpm-style packages. - Remove the legacy compiled F# extension compatibility layer; Terrabuild now supports only FScript
.fssextension scripts and rejects.fsxextension paths with a migration error. - Remove the Terrabuild scripting dependency on
FSharp.Compiler.Serviceby loading extension scripts exclusively through the FScript runtime. - Upgrade embedded FScript dependencies to
0.61.0, picking up the runtime fix that preserves missing optional JSON/XML record fields asNoneduring extension deserialization.
Full Changelog: 0.192.4-next...0.193.0-next
0.192.4
- Add a live
.NETremote-cache integration smoke test that runs the in-process graph pipeline through Docker, verifies@dotnet restore/buildcommand emission, and proves a cached project-reference target is restored without recompilation on a fresh worker cache. - Normalize repository identity before hashing projects and build graphs so equivalent local GitHub remotes and
GITHUB_REPOSITORYresolve to the same namespace while preserving multi-repository workspace separation by host/path. - Normalize GitHub repository owner/name case during repository hashing so local remotes like
git@github.com:MagnusOpera/Terrabuild.gitmatch CIGITHUB_REPOSITORY=magnusopera/terrabuild. - Support both dotted and bracketed project version lookups in expressions (
project.foo.version,project.["foo"].version,project.[terrabuild.project].version) and restore project-reference discovery so those expressions load referenced projects correctly during graph construction. - Add first-class
Repositorysource-control metadata to Terrabuild options, use it directly for remote Insights reporting, and include repository/origin identity in local project and graph hashes so cache keys remain stable across Git worktrees. - Upload build graph snapshots to Insights after
StartBuild(), including node execution metadata (artifacts,build,batch,action,required,isBatchNode) so downstream flow and architecture metrics can compute transitive graph impact. - Add artifact
startedAt/endedAttimestamps to Insights cache publication so Terrabuild sends per-target execution windows withadd-artifact.
Full Changelog: 0.191.1...0.192.4
0.192.4-next
- Add a live
.NETremote-cache integration smoke test that runs the in-process graph pipeline through Docker, verifies@dotnet restore/buildcommand emission, and proves a cached project-reference target is restored without recompilation on a fresh worker cache.
Full Changelog: 0.192.3-next...0.192.4-next
0.192.3-next
- Normalize repository identity before hashing projects and build graphs so equivalent local GitHub remotes and
GITHUB_REPOSITORYresolve to the same namespace while preserving multi-repository workspace separation by host/path. - Normalize GitHub repository owner/name case during repository hashing so local remotes like
git@github.com:MagnusOpera/Terrabuild.gitmatch CIGITHUB_REPOSITORY=magnusopera/terrabuild.
Full Changelog: 0.192.2-next...0.192.3-next
0.192.1-next
- Add first-class
Repositorysource-control metadata to Terrabuild options, use it directly for remote Insights reporting, and include repository/origin identity in local project and graph hashes so cache keys remain stable across Git worktrees. - Upload build graph snapshots to Insights after
StartBuild(), including node execution metadata (artifacts,build,batch,action,required,isBatchNode) so downstream flow and architecture metrics can compute transitive graph impact.
Full Changelog: 0.192.0-next...0.192.1-next
0.191.1
- Revert
+=-= - Revert
includesandoutputsoverrides
Full Changelog: 0.190.3...0.191.1
0.191.1-next
- Revert
+=-= - Revert
includesandoutputsoverrides
Full Changelog: 0.191.0-next...0.191.1-next
0.191.0-next
- Add ordered
outputsand project-targetdepends_onoperations (=,+=,-=), allowingPROJECTfiles to update outputs and to extend, remove, or replace workspace target dependencies in declaration order.
Full Changelog: 0.190.3-next...0.191.0-next
0.190.3
- Fix cache summary generation to omit the
outputsartifact marker when batched or managed builds did not materialize any outputs, avoiding broken restore attempts against non-existent output archives. - Fix cache artifact publication to send logical file names (
logs,outputs) to Insights while keeping full<ProjectHash>/<Target>/<TargetHash>/...storage keys internal to cache uploads. - Change project-level
includesandoutputsto act as true overrides of inferred/default values instead of being merged implicitly. - Reuse existing artifacts for batched
Restoremembers by linking them to the current build withuse-artifactinstead of republishing cache/artifact state after batch execution.
Full Changelog: 0.189.22...0.190.3
0.190.3-next
- Fix cache summary generation to omit the
outputsartifact marker when batched or managed builds did not materialize any outputs, avoiding broken restore attempts against non-existent output archives.
Full Changelog: 0.190.2-next...0.190.3-next