-
Notifications
You must be signed in to change notification settings - Fork 5
Expand file tree
/
Copy pathDirectory.Build.props
More file actions
30 lines (22 loc) · 1.76 KB
/
Copy pathDirectory.Build.props
File metadata and controls
30 lines (22 loc) · 1.76 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
<Project>
<PropertyGroup>
<VersionPrefix>0.8.1</VersionPrefix>
<VersionSuffix>beta</VersionSuffix>
<Copyright>Copyright (c) 2026 Quinten Martens <madq42@gmail.com></Copyright>
<!-- Pin transitive package versions in a committed packages.lock.json per project. -->
<RestorePackagesWithLockFile>true</RestorePackagesWithLockFile>
<!-- Deterministic (reproducible) builds in CI: ContinuousIntegrationBuild enables
/pathmap source normalization so binaries/PDBs carry no machine-specific paths.
CI-only (via GITHUB_ACTIONS) — setting it locally would break debugging by
pathmapping sources. Guarded on '' so an explicit -p:/env value still wins. -->
<ContinuousIntegrationBuild Condition="'$(ContinuousIntegrationBuild)' == '' and '$(GITHUB_ACTIONS)' == 'true'">true</ContinuousIntegrationBuild>
<!-- In CI, fail on a stale/incomplete lock file instead of silently regenerating it —
genuinely enforced (force-evaluate removed). This is durable because the restore graph
is stable: global.json pins the SDK (10.0.302), so SDK-versioned packages like
ILLink.Tasks don't drift, and RuntimeIdentifiers in RoslynMcp.csproj makes the graph
platform-independent (win-x64;linux-x64;osx-arm64), so one committed multi-RID
packages.lock.json satisfies every matrix platform. GITHUB_ACTIONS auto-fires in
every Actions workflow; ContinuousIntegrationBuild covers any non-Actions CI. -->
<RestoreLockedMode Condition="'$(GITHUB_ACTIONS)' == 'true' or '$(ContinuousIntegrationBuild)' == 'true'">true</RestoreLockedMode>
</PropertyGroup>
</Project>