If they explicitly pass in null or undefined we shouldn't attach the header to avoid issues like #154. In theory this could break someone, but only if all of the following conditions are met:
1) They are currently passing in null or undefined for the userAgent (not just ''). Note that this is not allowed by our typing, but some JS clients or TS clients without strict typing could in theory be doing this
2) The endpoint they are hitting requires a userAgent header but allows it to be empty
This feels pretty low risk to me so I think a minor version bump should be fine.
If they explicitly pass in null or undefined we shouldn't attach the header to avoid issues like #154. In theory this could break someone, but only if all of the following conditions are met:
1) They are currently passing in null or undefined for the userAgent (not just
''
). Note that this is not allowed by our typing, but some JS clients or TS clients without strict typing could in theory be doing this 2) The endpoint they are hitting requires a userAgent header but allows it to be emptyThis feels pretty low risk to me so I think a minor version bump should be fine.
Fixes #154