Repository navigation
Releases
6.8.0
Intro:
This release adds a way to get the range of time a FHIR date or dateTime covers at its
precision, and makes the FHIRPath conversion functions follow the FHIRPath specification for items
of a complex type: they no longer throw, but return empty or false. There are no breaking API
changes.
Date and time ranges
- New
Interval<T>andDateTimeRangetypes inHl7.Fhir.ElementModel.Types.Interval<T>is a
generic interval whose sides are closed, open or unbounded, withContains,Overlapsand
Covers.DateTimeRangeis a half-open range [Start,End) that also keeps thePrecision. DateandDateTimegetTryGetRange(out range),GetRange(TimeZoneInfo)and
GetRange(TimeSpan). For example,2026-03covers all of March 2026, and10:00:00+01:00covers
one second. A value without an offset is read in the given time zone, and the range is widened
where daylight saving skips or repeats a time.PeriodgetsTryGetRange(out range)andTryGetRange(TimeZoneInfo, out range), from the start
ofstartto the end ofend. A missing side is unbounded.DateTimenow keeps the number of fraction digits fromParse(), so.000spans 1 ms. See issue
#3628.
FHIRPath
-
The conversion functions
toBoolean(),toInteger(),toLong(),toDecimal(),toQuantity(),
toString(),toDate(),toDateTime()andtoTime()now return empty for an item of a type
they cannot convert, such as a complex type or a resource, and the matchingconvertsTo*()
functions returnfalse, as the FHIRPath specification
requires.Patient.name.first().convertsToString()used to throw anInvalidOperationException
("There is no known Cql/FhirPath type corresponding to the .NET type PocoNode") and now returns
false. The same goes for aCodingwithout acode, and aQuantitywithout a value or with a
comparator. Items with a System type equivalent, likeQuantity, convert as before. See issue #3636.Behavioural note: if you added your own overload of one of these functions to a
SymbolTable
that already has the standard functions, with aPocoNodeparameter, the standard function now
takes precedence for complex types too. Register your overload in a childSymbolTableto keep
it in effect.
Changes:
- #3637: Fix FHIRPath conversions on complex types
- #3629: Add date and dateTime ranges by precision
- #3636: FHIRPath conversion functions throw on complex types instead of returning empty/false
- #3635: Release 6.7.0
- #3630: Bump the runtime-dependencies-minor group with 4 updates
This list of changes was auto generated.
6.7.0
Intro:
This release adds an opt-in PrimitiveValueConverter hook to the POCO deserializers, makes the
JSON parser reject a primitive whose value is supplied twice, keeps repeated same-url extensions in
snapshots, makes the SnapshotGenerator report differential paths with an empty segment, and fixes
FHIRPath evaluation over invalid primitive values. LocalTerminologyService now returns the full
$validate-code result shape, and the terminology services accept repeated tx-resource
parameters. There are no breaking API changes, but several changes alter behaviour or output that
callers may depend on: the new fatal parser issue JSON135, the text of
OperationOutcome.IssueComponent.ToString(), warnings on inactive codes from $validate-code, and
$expand rejecting repeated 0..1 parameters. See the behavioural notes below.
Serialization
-
New
DeserializerSettings.PrimitiveValueConverterlets callers fix a wrongly typed primitive while
parsing, such as"valueInteger": "42"or"active": "true", in both Json and Xml and in every
mode,Ostrichincluded. It is called only for values that are not of the type the primitive
stores, plusdate,dateTime,instant,timeandinteger64, which can be the right type in
the wrong format. If it declines (returns the input) or throws aFormatException,
InvalidCastExceptionorOverflowException, the usual error is reported; any other exception
propagates. When not set, parsing is unaffected. -
The string overloads of the Json deserializers now encode into a pooled buffer instead of
allocating a freshbyte[]per parse, and the reader options the SDK uses are now public as
SerializationUtil.FhirJsonReaderOptions. See issue #3598. -
An exception thrown while reading an Xml attribute is no longer hidden behind
"Can only exit from a resource part.". -
The JSON parser now reports a fatal issue,
JSON135(PRIMITIVE_VALUE_SUPPLIED_TWICE), when a
primitive gets its value from bothnameand_name, e.g.{"name":"John","_name":"Johnny"}.
The second value used to be dropped silently, with only the non-fatalJSON134, so the
NoOverflow,RecoverableandBackwardsCompatiblemodes accepted the data loss. This applies in
either property order and to elements of primitive arrays.JSON134stays a non-fatal error for
a primitive under_namewhen no value was set yet. See issue #3533.Behavioural note: JSON that parsed before, with a non-fatal
JSON134, now fails to parse in
every mode exceptOstrichwhen bothnameand_namecarry a value.
FHIRPath
- An unparseable
instant,integer64,integer,positiveIntorunsignedIntvalue no longer
makes almost every FHIRPath expression that reaches it throw. Its value is now the unparsed
string, as it already was fordate,dateTimeandtime. Before, even$this is Reference
threw anInvalidOperationExceptionfor such a node, so a sweep like
descendants().where($this is Reference)failed on the whole resource. TheValuegetter of the
POCO still throws.
Snapshot generation
- The
SnapshotGeneratornow reports a specific issue (PROFILE_ELEMENTDEF_INVALID_PATH, code
10021) for a differential element whose path has an empty segment, such asObservation...unit,
and skips that element. Such an element used to produce a phantom elementObservation.in the
snapshot, and any constraint on it, like afixedString, was silently lost. The rest of the
differential is still processed. See issue #3591. - When a differential has several extensions with the same url, e.g. repeated
additional-binding
extensions on a binding, and the base already has one with that url, the snapshot now keeps all of
them. The first replaces the base extension, the rest are added next to it. They used to overwrite
each other, so only the last one survived. See issue #3625.
Terminology
-
LocalTerminologyService's ValueSet$validate-codenow returns the full result shape the HL7
terminology ecosystem tests expect:code,system,versionanddisplay, plus anissues
OperationOutcome with tx-issue-type codings and expressions relative to the input, for both valid
and invalid codes. ACodeableConceptinput is echoed back, and inactive or non-active concepts
getinactive/statusparameters.ValidateCodeResulthas new properties to read and write
these (CodeableConcept,NormalizedCode,CausedByUnknownSystem,UnknownSystem,Inactive,
Status), and newAdd*extension methods put an issue in itsissues. See issue #3631.Behavioural note: an inactive, retired or deprecated code now returns
result = truewith a
message(acode-commentwarning). For an unknown system,messagenow also says the
CodeSystem could not be found. -
The terminology services no longer reject an operation with repeated
tx-resourceparameters,
which the tx-ecosystem IG requires servers to accept. Only repeats of the operation's 0..1
parameters are rejected; known 0..* and unknown parameters pass through. Each typed*Parameters
class now lists its parameters in a publicKnownParameters.Behavioural note:
$expandnow gets the same check, so a repeatedurl,filter,count
etc. is rejected where it used to be accepted.
Other
-
PocoNode.Resolve("#id")no longer throws aNullReferenceExceptionwhen the resource has a
contained resource without anidbefore the one it refers to. A contained resource without an
iddoes not match, and resolution continues. See issue #3613. -
OperationOutcome.IssueComponent.ToString()now writes a space before(further diagnostics:,
as it already did before(at. See issue #3621.Behavioural note: this changes the rendered text of an issue. Tests that compare against
ToString()output need new expected strings.
Changes:
- #3634: VONK-10389: Allow repeated tx-resource parameters
- #3633: Return the full $validate-code result shape from LocalTerminologyService
- #3631: Extend ValidateCodeResult with the full $validate-code output and fill it from LocalTerminologyService
- #3627: VONK-10125: Add opt-in primitive value converter to the POCO deserializers, pool Json string parsing
- #3598: POCO deserialization: byte/stream entry points and pooled re-encoding of JSON strings
- #3626: Keep repeated same-url extensions in snapshots
- #3625: Snapshot generator loses repeated extensions with the same URL (e.g. additional-binding) when the base already has one
- #3624: Bump the runtime-dependencies-minor group with 2 updates
- #3623: Make FHIRPath tolerate unparseable primitive values
- #3616: Document the changes for release, bump version to 6.6.0
See More
- #3622: Add space before "(further diagnostics:" in issue ToString
- #3619: Add test for Base-typed inline children (#3597)
- #3597: SnapshotGenerator: inline children of a new element typed
Baseare emitted one level up (segment dropped from path and id) - #3620: Report and skip '..' in differential paths
- #3618: Report fatal error when name and _name both set
- #3533: JSON deserializer silently drops a primitive value when both 'name' and '_name' supply one (non-fatal)
- #3617: Fix Resolve NRE on contained resource w/o id
- #3591: SnapshotGenerator: '..' in differential path produces phantom element and silently drops the constraint
- #3576: feat: add the missing NOOVERFLOW preset to both deserializers (#3532)
- #3613: PocoNode.Resolve throws NullReferenceException when a contained resource has no id
This list of changes was auto generated.
6.6.0
Intro:
This release adds net10.0 to the frameworks the SDK targets, next to net8.0 and
netstandard2.1. It also lets FhirClient send a resource directly as the body of an operation
request, extends the FHIRPath htmlChecks() function to string input, and makes the
SnapshotGenerator report differential elements that are out of order. There is one binary
breaking change: ElementNavFhirExtensions.HtmlChecks(PocoNode) now returns bool? instead of
bool. Code that calls it needs to be recompiled. See the FHIRPath notes below.
Platform support
- The SDK now also targets
net10.0, next tonet8.0andnetstandard2.1. This is additive: .NET 8
and .NET 9 applications keep resolving to thenet8.0assets. On .NET 10, class mapping lookups
by name throughModelInspector.FindClassMapping(ReadOnlySpan<char>)no longer allocate. net8.0remains supported until the next major version (SDK 7), even after Microsoft ends support
for .NET 8 in November 2026.- Upcoming:
netstandard2.1will be removed in a later minor release, once Unity 6.8 - which
replaces Mono with CoreCLR and .NET 10 - has shipped. Its only remaining audience is Unity, and
Unity 6.8 can consume thenet10.0assets. If you depend on thenetstandard2.1assets for
another platform, please let us know.
FhirClient
- Operations with exactly one resource input can now send that resource directly as the POST body,
instead of wrapping it in aParametersresource.WholeSystemOperationAsync,
TypeOperationAsync,InstanceOperationAsyncandOperationAsynchave new overloads that take a
Resource, andTransactionBuilderhas matching overloads for its operation entries. The
existingParametersoverloads are unchanged. See issue #3599.
FHIRPath
htmlChecks()can now be invoked on astring. Its contents are validated as the content of a
narrativediv, following the current FHIRPath build (FHIR-56303).
Invoked on anything other thanxhtmlor astring, it now returns empty instead offalse. To
support this,ElementNavFhirExtensions.HtmlChecks(PocoNode)returnsbool?instead ofbool,
which is a binary breaking change for code that calls it directly. See issue #3604.
Snapshot generation
- The
SnapshotGeneratornow reports a specific issue (PROFILE_ELEMENTDEF_INVALID_ELEMENT_ORDER,
code 10020) when a differential element is out of order, i.e. when it constrains a base element
that precedes a base element already matched by an earlier differential element. The spec
requiresdifferential.elementandsnapshot.elementto follow the order of the base
definition. Such elements could previously not be matched and were silently treated as new
elements, which surfaced downstream as a confusing error. The generator does not reorder the
differential. See issue #3600.
Dependencies
- The
System.Reflection.Emit.LightweightandSystem.Bufferspackage dependencies were removed;
both are part of every framework the SDK targets. - Updated Microsoft.SourceLink.GitHub to 10.0.401. MSTest (4.4.1) and Verify.MSTest (33.1.5) were
updated too, but are test-only and not part of the shipped packages.
Changes:
- #3612: VONK-10067: Add net10.0 target framework and convert to slnx
- #3614: Bump the runtime-dependencies-minor group with 1 update
- #3609: Bump the runtime-dependencies-minor group with 2 updates
- #3601: Report a clear issue for out-of-order differential elements in SnapshotGenerator
- #3602: Support resource-body operation overloads
- #3605: Support FHIRPath htmlChecks() on string input
- #3608: Bump Microsoft.SourceLink.GitHub from 10.0.400 to 10.0.401
- #3607: Bump MSTest.TestFramework and Verify.MSTest
- #3603: Release 6.5.0
- #3600: SnapshotGenerator doesn't sort out-of-order differential/snapshot elements (unlike HAPI's Java validator)
This list of changes was auto generated.
6.5.0
Intro:
This release is mostly about the cost of parsing and serializing: allocations on the hot path of
(de)serialization are down substantially, and the serializers no longer emit empty objects or
elements. It also collects a series of SnapshotGenerator fixes and a concurrency fix in
terminology validation. There are no breaking API changes, but two SnapshotGenerator
OperationOutcome issue codes were renumbered to remove duplicates (10012 -> 10018,
10014 -> 10019), which affects code that switches on those numbers. See the behavioural
notes below.
Serialization
- The serializers no longer write empty objects (
{}) or empty elements (<x/>). A structure is
opened only once it is known to have content, so an empty POCO - or one emptied out by a
SerializationFilter, as happens when summarizing - no longer produces output our own
deserializer rejects withOBJECTS_CANNOT_BE_EMPTY/ELEMENT_CANNOT_BE_EMPTY. Summarized
resources now round-trip. See issue #3557. - Both deserializers now expose a
NOOVERFLOWpreset, next toSTRICT.DeserializationMode.NoOverflow
was the one mode without a preset, reachable only by constructing the settings by hand. Thanks to
@sujeito-operator for the contribution. See issue #3532. new FhirUri((Uri)null)no longer throws aNullReferenceException;FhirUrl(Uri)and
Canonical(Uri)had the same problem. They now null-propagate, like the other primitive
datatype constructors. See issue #3578.
Performance
- Parsing allocates considerably less. Most of what a parse used to allocate was transient garbage
produced by model validation - which runs on every element in every deserialization mode except
SyntaxOnlyandOstrich- rather than the POCO graph it returns. Validation now allocates about
half of what it did, and the validation outcomes are unchanged. Measured on a Patient
StructureDefinition (88 KB): 5.1 MB allocated and 3.4 ms per parse, down to 2.5 MB and 1.8 ms.
With the validator off, the same parse went from 1.4 MB to 1.0 MB. - The
ClassMappinghot path no longer allocates per access. Two patterns - aLazyInitializer
factory allocated on every call, including the warm path, and a full locked snapshot of the
property mapping collection - sat on the per-element path of every (de)serialization and are now
gone. - Serialization caches encoded JSON property names, and class mapping lookups are allocation-free
on .NET 10 and later (ClassMappingCollection.FindByName(ReadOnlySpan<char>)), with a fallback
on earlier frameworks.
Snapshot generation
- Fixed a
NotSupportedException("Can only jump to local nameReferences") when a differential
element carried a complex type profile reference of the formcanonicalUrl#elementNameand
had child constraints. See issue #3583. - Logical models deriving directly from
Base- which is only a resolvableStructureDefinition
from R5 onwards - are now handled gracefully. Before R5,Baseis treated as an empty root and a
warning is emitted instead of the generator failing. Element matching and child handling for
anonymous and untyped logical model elements were improved along with it (VONK-10132). - Two
OperationOutcomeissue codes were each used for two unrelated conditions. The duplicates
have been resolved:PROFILE_ELEMENTDEF_SLICENAME_NOMATCHmoves from 10012 to 10018, and
PROFILE_STRUCTURE_TYPE_MISSINGmoves from 10014 to 10019. Code that switches on these
numeric codes needs updating. See issue #3587.
Terminology
LocalTerminologyService(multi-codingCodeableConceptvalidation) andValueSetExpander
(grouping value sets) fanned out withTask.WhenAll, so a single logical operation could call
back into the caller-suppliedIAsyncResourceResolverfrom several threads at once. A resolver
that is not safe for concurrent use - a scoped EF Core-backed resolver, for instance - failed
with "A second operation was started on this context instance". Both sites now resolve
sequentially. See issue #3582.
Other
- Dynamic type inference in
NewPocoBuildernow uses the FHIR definition, where available, to
decide whether an element is primitive or complex, rather than relying on type-name heuristics.
This fixes misclassification of complex types in logical models identified by a canonical url. MatchesPrefixno longer compares aReadOnlySpan<char>againstnull(CA2265). This is not a
behaviour change - the comparison was correct - but it blocked building againstnet10.0under
TreatWarningsAsErrors. See issue #3580.
Dependencies
- Updated Microsoft.SourceLink.GitHub to 10.0.400. NSubstitute (6.2.0) and Verify.MSTest (32.0.0)
were updated too, but are test-only and not part of the shipped packages.
Changes:
Bugfixes:
- #3583: SnapshotGenerator crashes with NotSupportedException on complex type profile reference (url#element) with child constraints
Others:
- #3594: Bump Verify.MSTest from 31.28.0 to 32.0.0
- #3593: [WIP] Fix duplicate OperationOutcome issue codes 10012 and 10014 in SnapshotGenerator
- #3592: Fix concurrent calls into caller-supplied resolver during terminology validation/expansion
- #3582: Terminology stack issues concurrent calls to the caller-supplied resolver via internal
Task.WhenAll - #3586: Fix SnapshotGenerator crash on complex type profile reference with child constraints
- #3585: Bump the runtime-dependencies-minor group with 1 update
- #3581: Replace span-vs-null comparison in MatchesPrefix (CA2265)
See More
- #3580: StringExtensions.MatchesPrefix: span-vs-null comparison trips CA2265 and blocks a net10.0 target
- #3579: Fix NullReferenceException in FhirUri(Uri) constructor
- #3577: VONK-10132: Adapt SnapshotGenerator handling of CDSHooks logical models
- #3576: feat: add the missing NOOVERFLOW preset to both deserializers (#3532)
- #3532: Missing NOOVERFLOW static preset on FhirXmlDeserializer/FhirJsonDeserializer
- #3575: Tweak dynamic type inference logic for NewPocoBuilder
- #3572: Halve the allocations of parse-time validation
- #3574: Bump the runtime-dependencies-minor group with 1 update
- #3558: Improve serialization performance by caching encoded property names
- #3570: Release 6.4.0
- #3569: Prune empty objects via token-deferring writers
- #3564: Remove allocations from ClassMapping hot path
This list of changes was auto generated.
6.4.0
Intro:
This release adds opt-in retention of XML comments in the POCO-based parser. There are no breaking changes.
Serialization
-
The POCO-based XML parser can now retain the comments found in the source document. Set
DeserializerSettings.RetainCommentstotrue(the default remainsfalse) and comments are attached to the parsed POCOs asSourceCommentsannotations, so that they survive a parse/serialize round-trip. See issue #3561.Behavioural note: the XML serializer now writes any
SourceCommentsannotation it encounters. Previously only POCOs produced by the legacy parser carried such annotations, so in practice nothing was written for POCOs coming from the new parser. If your code addsSourceCommentsannotations itself, those comments will now show up in serialized output.
Dependencies
- Updated Fhir.Metrics, Microsoft.SourceLink.GitHub, MSTest.TestFramework and Verify.MSTest to their latest versions. NSubstitute was updated to 6.0.0 (test-only, not part of the shipped packages).
Changes:
- #3567: Bump the runtime-dependencies-minor group with 3 updates
- #3562: Retain XML comments in the POCO-based parser
- #3561: Support retaining XML comments in the POCO-based parser
- #3560: Bump the runtime-dependencies-minor group with 3 updates
- #3556: Bump NSubstitute from 5.3.0 to 6.0.0
- #3554: Start development cycle 6.3.1
This list of changes was auto generated.
6.3.0
Intro:
This release includes a behavioral change in parsing alongside a minor bug fix. Please read the notes below carefully before upgrading.
POCO / type system
-
The SDK now detects incorrectly cased element and resource type names. Two new error codes are introduced:
PVAL131(WRONG_CASED_ELEMENT) andPVAL132(WRONG_CASED_RESOURCE_TYPE).Breaking change: Parsers running in strict mode will now report errors when receiving data with incorrectly cased element or resource type names. Data that was previously silently corrected during parsing will now cause parse errors instead. Make sure your data sources use the correct casing as defined by the FHIR specification. All non-strict modes (BackwardsCompatible, Recoverable, NoOverflow, and the default) continue to bind leniently, preserving the behaviour from previous SDK versions. The exact handling of wrong-cased names in lenient modes is subject to change in future major versions of the SDK.
Other fixes
- Fixed redundant null-checks and initialization logic in bundle link handling.
Changes:
- #3553: Potential fix for code scanning alert no. 1: Workflow does not contain permissions
- #3541: Remove redundant null-checks and initialization logic from
setLinkmethod - #3552: Bump the runtime-dependencies-minor group with 1 update
- #3540: Fix #3502: Detect wrong-cased element and resource type names at the model level
- #3502: Standardize case-sensitivity handling in JSON & XML parsers
- #3539: Start development cycle 6.2.2
- #3538: Add JetBrains Rider settings to .gitignore
This list of changes was auto generated.
6.2.1
Intro:
This is a bugfix release with several stability and correctness improvements.
Serialization
- Fixed an
OverflowExceptionwhen serializing large decimal values with old parsing stack - Switched
FhirClientto use the modern POCO serializer for better consistency- If legacy serializers are still needed, our choice can be overriden by assigning
Settings.SerializationEnginean instance ofFhirSerializationEngineFactory.Legacy.FromParserSettings(ModelInfo.ModelInspector, Settings.ParserSettings ?? new())as it was before
- If legacy serializers are still needed, our choice can be overriden by assigning
- Fixed size limitations when serializing base64-encoded data
- Fixed the
prettyoption being ignored when callingToXml()
Snapshot generation
- Fixed incorrect behavior in collection merge when suppression extensions were involved, which could cause an index-out-of-range error or suppression being silently ignored
POCO / type system
ISourceNodenow has a directToPoco()extension method- Fixed
instantvalues being stored incorrectly when converting from an untyped source - Untyped sources are now correctly associated with the model when building POCOs
- Custom resources and datatypes are now easier to define and build as a
ClassMappingforModelInspector - Restored collection initializer syntax support on the
Parametersclass - Added
IVersionableConformanceResourceto R5NamingSystem
Other fixes
- Resolver base class now allows returning
null, leaving it to the caller to decide whether to throw - Dependencies downgraded to align with the target framework version
Changes:
- #3535: Added more tests cases for unit tests. Some code cleanup.
- #3536: Pretty parameter is not being used in ToXml extension method.
- #3534: Fix: store 'instant' as canonical string when building a POCO from an untyped source
- #3531: Fix serialization base64 size limits
- #3472: Add direct ISourceNode.ToPoco() implementation
- #3526: Fixed incorrect merge logic in mergeCollectionWithSuppression that could result in suppression extension not being honoured
- #3530: Skip major version update rules for specific dependencies
- #3527: Bump the runtime-dependencies-minor group with 1 update
- #3509: Central Package Dependency Management AND LTS/Condition Suggestions
- #3525: Optimize serialization locking
See More
- #3523: Logic in mergeCollectionWithSuppression could result in an Index Out Of Range exception.
- #3521: Rebind untyped sources to builder's inspector in NewPocoBuilder
- #3520: Implement Central Package Management (CPM)
- #3508: Implement Central Package Management (CPM)
- #3516: Bump the runtime-dependencies-minor group with 1 update
- #3519: Support custom resources and datatypes in ClassMapping/ModelInspector
- #3518: Add Version interface to R5 NamingSystem
- #2850: Change ClassMappings so it can support custom resources
- #3517: fix: restore collection initializer support on Parameters class
- #3480: Fix OverflowException for large decimals, switch FhirClient to POCO serializer
- #3447: Parameters class in SDK 6 cannot be used with collection initializers like in older SDK
- #3514: Fix ResolverResult nullability annotations
- #3512: Relax resolve in base class to allow null, let caller decide about throwing
- #3507: Bump runtime deps and align MSTest adapter
- #3503: Fix DebuggerDisplay attribute for Url property on Extension.cs
- #3500: R6 related fixes
- #3498: Start development cycle 6.2.1
- #3473: Fix XmlReader field name collision in DeserializationBenchmark
This list of changes was auto generated.
New Contributors
- @rdeveen made their first contribution in #3503
- @MadhukarJukanti made their first contribution in #3517
- @granadacoder made their first contribution in #3508
6.2.0
Intro:
- Added a
RespectSuppressExtensionsetting toSnapshotGeneratorSettings(default:true) to allow consumers to opt out of suppress-extension handling during snapshot generation. - Added
Base.ClearOverflow()and corrected theNoOverflowdocstring. ITypedElementextension methods now useOverloadResolutionPriority(1), ensuring they are preferred overISourceNodeextensions for types implementing both interfaces (such asPocoNode).- Fixed a cache key issue in
CachingTerminologyServicewhere resource or unrecognized parameter values could produce invalid cache keys. - Validation now includes canonicals in failed resolve attempts, and cardinality validation correctly handles cases where no member name is reported.
- Updated
System.Text.JsonandMicrosoft.Extensions.Caching.Memoryto version10.0.7.
Changes:
- #3492: Bump Microsoft.Extensions.Caching.Memory and 4 others
- #3496: Skip build stages when only docs change (DEVOPS-706, DEVOPS-709)
- #3491: Added RespectSuppressExtension to SnapshotGeneratorSettings
- #3490: Fix small bug in the CachingTerminologyService
- #3487: Bump the test-dependencies group with 1 update
- #3483: Bump the runtime-dependencies-minor group with 4 updates
- #3479: Add ClearOverflow() to Base and fix misleading NoOverflow docstring
- #3475: Handle the case of cardinality validation not reporting membername
- #3470: Include canonicals in failed resolve attempts
- #3477: Add OverloadResolutionPriority to ITypedElement extensions
6.1.1
Intro:
Fixes wrong logic for BaseTerminologyService filtering parameters for duplicates on requests that accept 0..* on some parameters
Changes:
- #3464: Remove NoDuplicates from operations that allow for multiple params
- #3463: Merge support/sdk5 into develop (SDK5 → SDK6 sweep)
This list of changes was auto generated.