update CHANGELOG and known issues section README

Author: Blind-Striker

CHANGELOG.md

@@ -1,5 +1,50 @@
 # LocalStack .NET Client Change Log
 
+### [v1.5.0](https://github.com/localstack-dotnet/localstack-dotnet-client/releases/tag/v1.5.0)
+
+#### 1. New Features
+
+- **Added Endpoints from [Localstack Python Client](https://github.com/localstack/localstack-python-client) v2.7:**
+  - **RAM**
+  - **AppConfigData**
+  - **Pinpoint**
+  - **EventBridge Pipes**
+
+#### 2. General
+
+- **Framework Support Updates:**
+  - **.NET 8** support added.
+  - **Deprecated** support for **.NET 7** and **.NET 4.6.1**.
+  - Continued support for **.NET Standard 2.0** to maintain compatibility with older .NET versions.
+  - **Upcoming Changes:**
+    - In the next release, **.NET 6** support will be removed as it reaches end-of-life in November 2024.
+
+- **Functional Tests Enhancements:**
+  - **Removed** tests for legacy LocalStack versions and versions **v2.0** and **v2.2**.
+    - **Note:** LocalStack.NET no longer guarantees compatibility with these versions.
+  - **Added** functional test support for LocalStack versions:
+    - **v2.3**
+    - **v3.4**
+    - **v3.7.1**
+  - **New Tests:**
+    - Introduced new tests for **CloudFormation**.
+
+- **Package Updates:**
+  - **AWSSDK.Core** minimum version set to **3.7.400.30**.
+
+- **Testing Compatibility:**
+  - Successfully tested against LocalStack versions:
+    - **v1.3.1**
+    - **v2.3**
+    - **v3.4**
+    - **v3.7.1**
+
+#### 3. Warnings
+
+- **Breaking Changes Postponed:**
+  - The planned breaking changes have been postponed to the next release.
+  - **Important:** Users should anticipate some breaking changes in the next release due to the removal of legacy support and configuration updates.
+
 ### [v1.4.1](https://github.com/localstack-dotnet/localstack-dotnet-client/releases/tag/v1.4.1)
 
 #### 1. New Features

README.md

@@ -129,6 +129,8 @@ The `RegionName` is important as LocalStack creates resources based on the speci
 
 ## Known Issues
 
+- **SNS with LocalStack v3.7.2 and v3.8.0:** During development on the new version, it was discovered that SNS functional tests are not working in LocalStack versions v3.7.2 and v3.8.0. This issue was reported in LocalStack [issue #11652](https://github.com/localstack/localstack/issues/11652). The LocalStack team identified a bug related to handling SNS URIs and resolved it in [PR #11653](https://github.com/localstack/localstack/pull/11653). The fix will be included in an upcoming release of LocalStack. In the meantime, if you're using SNS, it is recommended to stick to version v3.7.1 of LocalStack until the fix is available.
+
 - **LocalStack Versions v2.0.1 - v2.2:** In versions v2.0.1 through v2.2 of LocalStack, the URL routing logic was changed, causing issues with SQS and S3 operations. Two issues were opened in LocalStack regarding this: [issue #8928](https://github.com/localstack/localstack/issues/8928) and [issue #8924](https://github.com/localstack/localstack/issues/8924). LocalStack addressed this problem with [PR #8962](https://github.com/localstack/localstack/pull/8962). Therefore, when using LocalStack.NET, either use version v2.0 of LocalStack (there are no issues with the v1 series as well) or the upcoming v2.3 version, or use the latest v3 series container from Docker Hub.
 
 - **AWS_SERVICE_URL Environment Variable:** Unexpected behaviors might occur in LocalStack.NET when the `AWS_SERVICE_URL` environment variable is set. This environment variable is typically set by LocalStack in the container when using AWS Lambda, and AWS also uses this environment variable in the live environment. Soon, just like in LocalStack's official Python library, this environment variable will be prioritized by LocalStack.NET when configuring the LocalStack host, and there will be a general simplification in the configuration. You can follow this in the issues [issue #27](https://github.com/localstack-dotnet/localstack-dotnet-client/issues/27) and [issue #32](https://github.com/localstack-dotnet/localstack-dotnet-client/issues/32). You set the `AWS_SERVICE_URL` to empty string until this issue is resolved.