Release v0.14.1 (#83)

* Prepare for releasing v0.14.1

* Add communication section in README

* Update CHANGELOG

CHANGELOG.md

@@ -8,6 +8,8 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 ## [Unreleased]
 
+## [0.14.1] - 2022-04-07
+
 ### Changed
 
 - Upgrade OTel to `v1.6.2`. (#82)
@@ -135,7 +137,8 @@ It contains instrumentation for trace and depends on OTel `v0.18.0`.
 - Example code for a basic usage.
 - Apache-2.0 license.
 
-[Unreleased]: https://github.com/XSAM/otelsql/compare/v0.14.0...HEAD
+[Unreleased]: https://github.com/XSAM/otelsql/compare/v0.14.1...HEAD
+[0.14.1]: https://github.com/XSAM/otelsql/releases/tag/v0.14.1
 [0.14.0]: https://github.com/XSAM/otelsql/releases/tag/v0.14.0
 [0.13.0]: https://github.com/XSAM/otelsql/releases/tag/v0.13.0
 [0.12.0]: https://github.com/XSAM/otelsql/releases/tag/v0.12.0

README.md

@@ -93,3 +93,7 @@ The project follows the [Release Policy](https://golang.org/doc/devel/release#po
 Based on [this comment](https://github.com/open-telemetry/opentelemetry-go-contrib/pull/505#issuecomment-800452510), OpenTelemetry SIG team like to see broader usage and community consensus on an approach before they commit to the level of support that would be required of a package in contrib. But it is painful for users without a stable version, and they have to use replacement in `go.mod` to use this instrumentation.
 
 Therefore, I host this module independently for convenience and make improvements based on users' feedback.
+
+## Communication
+
+I use GitHub discussions/issues for most communications. Feel free to contact me on CNCF slack.

version.go

@@ -16,5 +16,5 @@ package otelsql
 
 // Version is the current release version of otelsql in use.
 func Version() string {
-	return "0.14.0"
+	return "0.14.1"
 }