Update changelog entry

Author: EmilianoSanchez

CHANGES.txt

@@ -1,4 +1,7 @@
-2.1.1 (April 8, 2025)
+2.1.2 (April XX, 2025)
+ - Updated development dependencies to use React v19 and TypeScript v4.5.5 to test compatibility and avoid type conflicts when using the SDK with React v19 types.
+
+2.1.1 (April 9, 2025)
  - Bugfixing - Fixed `useSplitClient` and `useSplitTreatments` hooks to properly respect `updateOn<Event>` options. Previously, if the hooks were re-called due to a component re-render, they used the latest version of the SDK client status ignoring when `updateOn<Event>` options were set to `false` and resulting in unexpected changes in treatment values.
 
 2.1.0 (March 28, 2025)

src/__tests__/useSplitClient.test.tsx

@@ -251,7 +251,7 @@ describe('useSplitClient', () => {
     expect(currentStatus).toEqual(previousStatus);
 
     wrapper.rerender(<Component updateOnSdkUpdate={false} updateOnSdkTimedout={true} />); // trigger re-render because there was an SDK_READY_TIMED_OUT event
-    expect(rendersCount).toBe(4);
+    expect(rendersCount).toBe(4); // @TODO optimize `useSplitClient` to avoid double render
     expect(currentStatus).toMatchObject({ isReady: false, isReadyFromCache: false, hasTimedout: true });
 
     act(() => mainClient.__emitter__.emit(Event.SDK_READY)); // trigger re-render
@@ -266,7 +266,7 @@ describe('useSplitClient', () => {
     expect(currentStatus).toEqual(previousStatus);
 
     wrapper.rerender(<Component updateOnSdkUpdate={null /** invalid type should default to `true` */} />); // trigger re-render and update the status because updateOnSdkUpdate is true and there was an SDK_UPDATE event
-    expect(rendersCount).toBe(8);
+    expect(rendersCount).toBe(8); // @TODO optimize `useSplitClient` to avoid double render
     expect(currentStatus.lastUpdate).toBeGreaterThan(previousStatus.lastUpdate);
 
     act(() => mainClient.__emitter__.emit(Event.SDK_UPDATE)); // trigger re-render because updateOnSdkUpdate is true