Releases: renalreg/python-mirth-client
Releases · renalreg/python-mirth-client
v4.0.1
What's Changed
- General improvements by @OliveraReeves in #71
- fixed issue that would have appeared when using pydantic > 2.0
Full Changelog: v4.0.0...v4.1.0
v4.0.0
What's Changed
- Dependency updates:
- pytest-cov: ^3.0.0 → ^4.0.0 (#53)
- mypy: ^0.981 → ^1.1 (#54, #63)
- black: ^22.1 → ^23.3 (#64)
- httpx: ^0.23.0 → >=0.23,<0.25 (#69)
- lxml: ^4.7.1 → ^5.2.2 (#68)
- sphinx-rtd-theme: >=0.5.1,<1.1.0 → >=0.5.1,<2.1.0 (#67)
- semver: ^2.13.0 → >=2.13,<4.0 (#66)
- pydantic: ^1.8.2 → >=1.8.2,<3.0.0 (#65)
- importlib-metadata: <5 → <7 (#59)
- feat(TNG-1034): Update Python version (#70)
Full Changelog: v3.2.0-1...v4.0.0
v3.2.0-1
Retrigger publish after working around PyCQA/bandit#951
v3.2.0
What's Changed
- Update mypy requirement from ^0.961 to ^0.981 by @dependabot in #52
- Add message reprocessing and post source_map argument
Full Changelog: v3.1.0...v3.2.0
v3.1.0
v3.0.0
What's Changed
- Update httpx requirement from >=0.18,<0.22 to >=0.18,<0.23 by @dependabot in #36
- Update mypy requirement from ^0.910 to ^0.931 by @dependabot in #35
- Update typing-extensions requirement from ^3.10.0 to >=3.10,<5.0 by @dependabot in #31
- Model tests from API examples by @jtc42 in #38
Breaking changes
- Removed all deprecated functions
- Default content_type for all requests set to XML
Internal changes
Full Changelog: v2.0.4...v3.0.0
v2.0.4
v2.0.3
v2.0.2
Changelog
- Only return sent message on POST for Mirth API versions recent enough to return the message ID
In newer versions of Mirth, the API actually tells you the ID of the message you just sent and we use this to quickly return the message it received. In older versions, Mirth doesn't tell you anything about the message you just sent. In this case we return nothing and don't check if the message actually got processed. Sorry!