Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump fo-dicom from 5.1.5 to 5.2.0 #276

Merged
merged 1 commit into from
Feb 3, 2025
Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 3, 2025

Bumps fo-dicom from 5.1.5 to 5.2.0.

Release notes

Sourced from fo-dicom's releases.

5.2.0

On February 3rd 2025 fo-dicom 5.2.0 was officially released.

This release contains the following bugfixes:

  • Fix bug where VOI LUT Function with empty value caused a crash (#1891)
  • Fixed bug, where milliseconds have been cut away when adding a Datetime to a DicomDataset (#1719)
  • Fix parsing of invalid DICOM files, that contain "," as decimal separator in DS values (#1296)
  • Fix parsing files from stream created by HttpClient (#1698)

This release contains the following changes:

  • Update to DICOM Standard 2024d
  • Add ConnectionTimeout to ClientConnectionOptions (#1784)
  • Refactor the parser to make it better maintainable
  • The optional AffectedSopInstanceUID is added to the CStoreResponse by default. (#1390)
  • 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)

There are the following breaking changes from version 5.1.5 to version 5.2.0

  • the IByteSource interface has changed
  • DicomElement.ValueRepresentation.ValidateString() now throws a DicomValidationException if a null value is passed (#1590)
Changelog

Sourced from fo-dicom's changelog.

5.2.0 (2025-02-03)

  • 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
Commits
  • a57583d prepare release 5.2.0
  • 06a1d0a Update to DICOM Standard 2024e
  • 42a30a7 update year 2025
  • a545625 Merge pull request #1928 from fo-dicom/GH-1927_dicomdir
  • 8be2d04 changelog
  • 7097fa6 in case the exact offset is not found, do not just look for the highest offse...
  • 11e3643 unittest to reproduce issue
  • 45c7a30 Merge pull request #1926 from fo-dicom/gh-1698_unseekable_networkstream
  • 29c2748 update changelog
  • 89ce0d4 wrap the read-loop into a loop so that the buffer is always filled correctly
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [fo-dicom](https://github.com/fo-dicom/fo-dicom) from 5.1.5 to 5.2.0.
- [Release notes](https://github.com/fo-dicom/fo-dicom/releases)
- [Changelog](https://github.com/fo-dicom/fo-dicom/blob/development/ChangeLog.md)
- [Commits](fo-dicom/fo-dicom@5.1.5...5.2.0)

---
updated-dependencies:
- dependency-name: fo-dicom
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added .NET Pull requests that update .net code dependencies Pull requests that update a dependency file labels Feb 3, 2025
@dependabot dependabot bot requested a review from a team February 3, 2025 14:23
@jas88 jas88 merged commit fa3af24 into develop Feb 3, 2025
3 checks passed
@dependabot dependabot bot deleted the dependabot/nuget/fo-dicom-5.2.0 branch February 3, 2025 15:10
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 .NET Pull requests that update .net code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant