Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 3, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
fo-dicom 5.1.5 -> 5.2.5 age adoption passing confidence

Release Notes

fo-dicom/fo-dicom (fo-dicom)

v5.2.5

Compare Source

  • Add INetoworkMetricsCollector, that is invoked by DicomService, to optionally collect metrics (#​2039)
  • Fix issue where creating an instance of ImageData when Pixel Spacing DICOM tags are present but empty causes an exception (#​2043)
  • Add support for constructing ImageData/VolumeData from multi-frame datasets (#​2015)
  • Added some private tags to dictionary (#​2027)
  • Rework disposing and cleanup of finished DICOM Clients in DicomServer (#​2046)
  • new interface IAsyncDicomService where OnConnectionClosedAsync and OnAbortAsync are invoked (#​2056)

v5.2.4

Compare Source

  • Fix issue where DicomFile.Clone did not do a deep-clone as expected (#​2025)
  • Fix referencing the wrong System.Text.Encoding.CodePages package (#​2021)
  • update to DICOM standard 2025d

v5.2.3

Compare Source

  • Add Milliseconds to result in DicomDataset.GetDateTime (#​1967)
  • Add convenience function to open and save in DicomStructuredReport (#​1968)
  • FO-DICOM.Tests target net9.0 instead of net6.0
  • Apply the sign to the minutes part of DatetimeOffsetFromUTC correctly (#​1988)
  • Add new functions TryGetDateTime and TryGetDateTimeOffset in DicomDataset (#​1988)
  • Fix issue where rescale slope/intercept were used from dataset in case a Modality LUT Sequence is present (#​1986)
  • allow rendering of images with empty rescale information (#​1975)
  • Prevent stack overflow in DicomDirectory by changing recursive to iterative method (#​1977)
  • Only accept even groups as Overlay Plane Module (#​1994)
  • Connect Options pattern with IConfiguration in setup (#​1940)
  • Breaking change: IDicomClientFactory does not have the parameters IOptions and IOptions any more. (#​1977)
  • Fix issue where all DicomMatchRules would not match any value (#​2010)
  • Fix memory leak in DicomServer (#​2009)
  • You can now specify port number 0 when creating a DicomServer to let the OS assign an available port, following standard socket API behavior. (#​1990)
  • update to DICOM standard 2025c

v5.2.2

Compare Source

  • render images with window width < 1, but apply LINEAR_EXACT on rendering (#​1905)
  • use current version of fo-dicom.Codecs in tests and DicomDump supporting Windows arm64 builds
  • new package Fo-Dicom.Imaging.SkiaSharp (#​1956)
  • Send Command and Data in separate PDUs (#​1960)
  • Fix opening an invalid file that contains some delimiter items at the end of the file (#​1958)
  • update to DICOM Standard 2025b

v5.2.1

Compare Source

  • Fixed regression in parser where group length of VR UN was parsed wrong (#​1941)
  • UseFellowOakDicom registers the default services only if there are not yet some services registered (#​1929)
  • update to DICOM Standard 2025a

v5.2.0

Compare Source

  • refactor the parser to make it better maintainable
  • Breaking change: IByteSource interface has changed
  • VOI LUT Function with empty value causes a crash (#​1891)
  • Add ConnectionTimeout to ClientConnectionOptions (#​1784)
  • Fixed bug, where milliseconds have been cut away when adding a Datetime to a DicomDataset (#​1719)
  • DicomElement.ValueRepresentation.ValidateString() now throws a DicomValidationException if a null value is passed (#​1590)
  • The optional AffectedSopInstanceUID is added to the CStoreResponse by default. (#​1390)
  • Handle invalid DICOM files, that contain "," as decimal separator in DS values (#​1296)
  • DicomDataset.AddOrUpdate also allows passing DicomSequence as argument type (#​1664)
  • Enable reading DICOMDIR files where the offsets are not correctly but at cleast close (#​1927)
  • Fix parsing files from stream created by HttpClient (#​1698)
  • update to DICOM Standard 2024e

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner February 3, 2025 13:45
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Feb 3, 2025
@renovate renovate bot changed the title Update dependency fo-dicom to 5.2.0 Update dependency fo-dicom to 5.2.1 Mar 13, 2025
@renovate renovate bot force-pushed the renovate/fo-dicom branch from 83ee0ae to baccc83 Compare March 13, 2025 11:26
@renovate renovate bot force-pushed the renovate/fo-dicom branch from baccc83 to 236510a Compare April 22, 2025 12:39
@renovate renovate bot changed the title Update dependency fo-dicom to 5.2.1 Update dependency fo-dicom to 5.2.2 Apr 22, 2025
@renovate renovate bot force-pushed the renovate/fo-dicom branch from 236510a to 52576da Compare September 18, 2025 13:32
@renovate renovate bot changed the title Update dependency fo-dicom to 5.2.2 Update dependency fo-dicom to 5.2.3 Sep 18, 2025
@renovate renovate bot force-pushed the renovate/fo-dicom branch from 52576da to c45baa3 Compare October 3, 2025 16:28
@renovate renovate bot changed the title Update dependency fo-dicom to 5.2.3 Update dependency fo-dicom to 5.2.4 Oct 3, 2025
@renovate renovate bot force-pushed the renovate/fo-dicom branch from c45baa3 to 7d230e1 Compare November 17, 2025 11:51
@renovate renovate bot changed the title Update dependency fo-dicom to 5.2.4 Update dependency fo-dicom to 5.2.5 Nov 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant