chore(v7): release 7.0.1 (#106)

🤖 I have created a release *beep* *boop*
---


##
[7.0.1](v7.0.0...v7.0.1)
(2024-03-01)


### Bug Fixes

* **deps:** bump golang.org/x/crypto from 0.1.0 to 0.17.0
([5d26f59](5d26f59))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "7.0.0"
+  ".": "7.0.1"
 }

CHANGELOG.md

@@ -2,6 +2,13 @@
 
 All notable changes to the LaunchDarkly Go SDK will be documented in this file. This project adheres to [Semantic Versioning](http://semver.org).
 
+## [7.0.1](https://github.com/launchdarkly/go-server-sdk/compare/v7.0.0...v7.0.1) (2024-03-01)
+
+
+### Bug Fixes
+
+* **deps:** bump golang.org/x/crypto from 0.1.0 to 0.17.0 ([5d26f59](https://github.com/launchdarkly/go-server-sdk/commit/5d26f59f915c62636d7ba8b0a06e00a6c6c3f677))
+
 ## [7.0.0] - 2023-10-11
 The latest version of this SDK supports the ability to manage migrations or modernizations, using migration flags. You might use this functionality if you are optimizing queries, upgrading to new tech stacks, migrating from one database to another, or other similar technology changes. Migration flags are part of LaunchDarkly's Early Access Program. This feature is available to all LaunchDarkly customers but may undergo additional changes before it is finalized.
 

internal/version.go

@@ -1,4 +1,4 @@
 package internal
 
 // SDKVersion is the current version string of the SDK. This is updated by our release scripts.
-const SDKVersion = "7.0.0" // {{ x-release-please-version }}
+const SDKVersion = "7.0.1" // {{ x-release-please-version }}