-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathDirectory.Build.props
More file actions
62 lines (57 loc) · 3.43 KB
/
Copy pathDirectory.Build.props
File metadata and controls
62 lines (57 loc) · 3.43 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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
<Project>
<PropertyGroup>
<LangVersion>12.0</LangVersion>
<Nullable>enable</Nullable>
<ImplicitUsings>enable</ImplicitUsings>
<EnableNETAnalyzers>true</EnableNETAnalyzers>
<AnalysisLevel>10-recommended</AnalysisLevel>
<EnforceCodeStyleInBuild>true</EnforceCodeStyleInBuild>
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
<Deterministic>true</Deterministic>
<DebugType>portable</DebugType>
<RestorePackagesWithLockFile>true</RestorePackagesWithLockFile>
</PropertyGroup>
<PropertyGroup Condition="'$(CI)' == 'true'">
<ContinuousIntegrationBuild>true</ContinuousIntegrationBuild>
<RestoreLockedMode>true</RestoreLockedMode>
</PropertyGroup>
<!-- Packaging identity every published package shares. A project says what
it is; where it came from and who to ask is the same answer for all of
them, so it is answered once. -->
<PropertyGroup>
<!-- One version for the whole repository, so "the LibTmux.Mcp that goes with
this LibTmux" is true by construction rather than by a compatibility
table somebody has to keep current.
A published version can never be deleted from nuget.org, only
unlisted, so the first one out is the lowest that still says what it
is. 0.0.0-0 is the lowest version NuGet accepts at all and tells a
reader nothing; this is the floor among the ones that say alpha, and
every 0.0.0-alpha.N, 0.0.1, 0.1.0 and 1.0.0 sorts above it. -->
<VersionPrefix>0.0.0</VersionPrefix>
<VersionSuffix>alpha.15</VersionSuffix>
<!-- One note for the suite, because one version covers it. Naming any
single package's changes here would put them on every other
package's page too, which is what this used to do. Why one version
covers the suite, and when that is revisited: ADR 0007. -->
<PackageReleaseNotes>Alpha. LibTmux, LibTmux.Testing, LibTmux.Query.Json, LibTmux.Extensions.DependencyInjection, LibTmux.Workspace and LibTmux.Mcp share one version, so this release covers them together. What changed, per package and per release: https://github.com/libtmux/libtmux-dotnet/blob/master/CHANGELOG.md The public API is not settled and may change without notice between prereleases; pin an exact version.</PackageReleaseNotes>
<Authors>Tony Narlock</Authors>
<Copyright>Copyright (c) 2026 Tony Narlock <tony@git-pull.com></Copyright>
<PackageLicenseExpression>MIT</PackageLicenseExpression>
<!-- The libtmux mark, shared with the Python original these packages carry
parity with. nuget.org takes PNG or JPEG only, so an SVG would have to
be exported before it could ship. -->
<PackageIcon>icon.png</PackageIcon>
<PackageProjectUrl>https://github.com/libtmux/libtmux-dotnet</PackageProjectUrl>
<RepositoryUrl>https://github.com/libtmux/libtmux-dotnet</RepositoryUrl>
<RepositoryType>git</RepositoryType>
<!-- Debugging a tmux problem means reading this library's source, so the
symbols and the sources they point at ship alongside each package. -->
<PublishRepositoryUrl>true</PublishRepositoryUrl>
<EmbedUntrackedSources>true</EmbedUntrackedSources>
<IncludeSymbols>true</IncludeSymbols>
<SymbolPackageFormat>snupkg</SymbolPackageFormat>
<!-- Publishing is opted into. A new test project, tool, or sample cannot
reach a feed by being forgotten about. -->
<IsPackable>false</IsPackable>
</PropertyGroup>
</Project>