chore: re-export yup_oauth2 as suggested by @Serpex

CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to this project will be documented in this file.
 
+## [0.20.0] - 2024-04-28
+
+### Maintenance
+
+- Re-export yup_oauth2 as suggested by @serpex.
+
 ## [0.19.0] - 2024-04-27
 
 ### Maintenance

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "gcp-bigquery-client"
-version = "0.19.0"
+version = "0.20.0"
 authors = ["Laurent Querel <laurent.querel@gmail.com>"]
 edition = "2018"
 license = "MIT OR Apache-2.0"

src/lib.rs

@@ -37,6 +37,10 @@ use crate::routine::RoutineApi;
 use crate::table::TableApi;
 use crate::tabledata::TableDataApi;
 
+/// Since yup_oauth2 structs are used as parameters in public functions there is already semver
+/// coupling, as it is an error if consumer uses different version of yup_oauth than gcp-bigquery-client
+/// Export yup_oauth2 so consumers don't need to carefully keep their dependency versions in sync.
+/// (see https://github.com/lquerel/gcp-bigquery-client/pull/86)
 pub use yup_oauth2;
 
 pub mod auth;