Repository navigation
1.21.0
Changed
-
Every first-party assembly now multi-targets
net10.0;net11.0(ADR 0015). .NET 11 shipped on 2026-11-10; .NET 8 and .NET 9 reached end of support the same day. ADR 0015's rule is to add a TFM the day a release ships and drop one the day Microsoft ends its support, so this is that rule firing for the first time rather than a judgement call.global.jsonpins SDK 11.0.100. That pin is load-bearing: SDK 10 cannot targetnet11.0, androllForward: latestFeaturewill not cross a major version, so an environment without SDK 11 fails the build outright instead of quietly producing net10-only packages.If you target
net8.0ornet9.0, stay on 1.20.0 — 1.21.0 carries no assets your project can resolve, and restoring it fails with NU1202 rather than falling back. Please read the next entry before you do: 1.20.0 is also the last release carrying a SARIF severity bug, and it is a security-relevant one. -
Tamp.NetCli.V8andTamp.NetCli.V9are retargeted, not retired. Their assemblies now load onnet10.0/net11.0, and they still wrap thedotnet 8anddotnet 9CLIs exactly as before. Which runtime a wrapper runs on and which CLI it drives are independent axes (ADR 0015), and locked-down environments keep older SDKs installed for years past EOL. Nothing about these packages' purpose changed. -
SARIF: an absentlevelnow reads asWarningon every target framework, instead ofNoneon some of them (#166). This is a behaviour change with security consequences, and the reason it surfaced now is worth stating.Tamp.Sarif's schema records are records with non-nullable properties carrying initializers —SarifLevel Level { get; init; } = SarifLevel.Warning, and eleven others. A property initializer like that is only honoured if the deserializer leaves absent JSON members alone. .NET 11'sSystem.Text.Jsonsource generator leaves them alone. Every earlier runtime overwrites the member withdefault(T).default(SarifLevel)isNone.So on net8, net9 and net10 — every runtime Tamp has ever shipped on — a SARIF result whose scanner omitted
levelwas read asSarifLevel.None, the least severe value, where the declared default wasWarning. Omitting it is legal: SARIF 2.1.0 §3.27.10 defers to the rule'sdefaultConfiguration, which itself defaults towarning. And because the value then round-tripped, Tamp wrote"level": "none"back into the evidence file — a finding of unknown severity recorded as benign.SecurityPipelineMetrics.LevelToTagtags the metric a gate reads from that value, so such a finding sat below any "warning and above" threshold. The other initialized properties could come back null the same way;log.Runs[0]on a log with norunsmember threw aNullReferenceException.Fixed by enforcing each declared default in the accessor rather than trusting the runtime: readonly backing fields with coercing
initaccessors. Deliberate choices inside that fix —- Coercion is null-only, not
IsNullOrEmpty.SarifMerge.Combinepicks the first non-emptyVersion/Schemaacross logs, which requiresnew SarifLog { Version = "" }to stay expressible. Levelkeeps a nullableLevelRawcompanion ([JsonPropertyName("level")]) so an explicit"level": "none"staysNoneand an absent one stays absent on write. Defaulting on read must not become asserting on write.SarifLog.Schemalost its initializer entirely;SarifWriternow stampsSarifLog.CanonicalSchemaon any log that has none. A property default would have been clobbered on read by every pre-net11 runtime, which is the whole bug — andSarifMergeneeds "no schema" to survive a parse as null.
Nine regression tests in
SarifDefaultsTests.cspin this, and they run per-TFM: revert the source fix and they fail on net10 and pass on net11, which is how the cause was confirmed rather than inferred. - Coercion is null-only, not
Added
-
Tamp.NetCli.V11— wrapper for the .NET 11 SDK CLI, starting at its own version per ADR 0002. Same surface asTamp.NetCli.V10. -
Tamp.Components.NetCli.V11— concretedotnetbodies for theTamp.Componentstarget shapes (ADR 0020) driving thedotnet 11CLI. ADR 0015 only commits to theNetCli.V{N}package, but a consumer whose build script targetsnet11.0and composes viaTamp.Componentsneeds this one:Tamp.Components.NetCli.V10drives SDK 10, which cannot buildnet11.0projects at all. -
SarifLog.CanonicalSchema— the SARIF 2.1.0 schema URI every log Tamp writes carries, exposed so consumers can assert on it instead of hardcoding the string. -
The shipped version is announced on an issue when its release is published (#164).
CONTRIBUTING.mdrequired every closing comment to name its release, but an issue closed before the release is cut can only promise one — and the promise is what gets forgotten. #151 and #155 were both closed with "I will comment the version when it is cut", both shipped in 1.20.0, and neither got the comment. The link existed in one direction only: from the release notes to the issue, never back.release.ymlnow runs.github/scripts/announce-release.shafter creating the Release. An issue is announced when both its number appears in the release notes and it carries the newawaiting-releaselabel. The intersection is deliberate: notes also cite issues for context ("tracked in #162", "see the epic #58"), so announcing on every cited issue would claim a version for work that did not ship — a false statement, which is worse than a missing comment. Announcing on every labelled issue would be wrong the other way, for a fix merged after the tag. A missing comment is recoverable and the label keeps it visible; a wrong one is not.Never fails a release: by that point the packages are public and irreversible, so a problem announcing is a warning and nothing more. The script is dependency-free so it copies into the satellites.
The publish job gains
issues: write, scoped to that job alone.
Packages for this release are on nuget.org, and the attached .nupkg files are the exact artifacts that were pushed.