From 45d34a5d873bc126f55d67f91b07ee2525a3104f Mon Sep 17 00:00:00 2001
From: Sebastian Stock <42280794+sostock@users.noreply.github.com>
Date: Mon, 14 Aug 2023 13:12:47 +0200
Subject: [PATCH] Release v1.16.3 (#676)

---
 NEWS.md      | 6 ++++++
 Project.toml | 2 +-
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/NEWS.md b/NEWS.md
index b3ff79e0..2c537ca2 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -1,5 +1,11 @@
 # Unitful.jl changelog
 
+## v1.16.3 (2023-08-14)
+
+* ![Bugfix:](https://img.shields.io/badge/-bugfix-purple) Calling `min` and `max` with quantities of different units can no longer return wrong results due to floating-point overflow in the unit conversion ([#675](https://github.com/PainterQubits/Unitful.jl/pull/675)).
+* ![Bugfix:](https://img.shields.io/badge/-bugfix-purple) `min` and `max` now handle quantities with `NaN` values correctly ([#675](https://github.com/PainterQubits/Unitful.jl/pull/675)).
+* ![Bugfix:](https://img.shields.io/badge/-bugfix-purple) `Base.hastypemax` is now correctly implemented for quantity types ([#674](https://github.com/PainterQubits/Unitful.jl/pull/674)).
+
 ## v1.16.2 (2023-08-05)
 
 * ![Bugfix:](https://img.shields.io/badge/-bugfix-purple) The conversion factors between units can no longer be wrongly calculated as `NaN`, `Inf`, or `0` (which could happen, e.g., in the case of large exponents). The conversion factor is now calculated correctly in more cases, and an error is thrown if it cannot be calculated due to floating-point over- or underflow ([#648](https://github.com/PainterQubits/Unitful.jl/pull/648)).
diff --git a/Project.toml b/Project.toml
index 58498ac6..008c379a 100644
--- a/Project.toml
+++ b/Project.toml
@@ -1,6 +1,6 @@
 name = "Unitful"
 uuid = "1986cc42-f94f-5a68-af5c-568840ba703d"
-version = "1.16.2"
+version = "1.16.3"
 
 [deps]
 ConstructionBase = "187b0558-2788-49d3-abe0-74a17ed4e7c9"