Update changelog txt

[suryaaki2]

Impact

• Bug fix (non-breaking change which fixes expected existing functionality)
• Enhancement/New feature (adds functionality without impacting existing logic)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

A clear and concise description of the change being made.

• Introduce what was/will be done in the title
  • Titles show in release notes and search results, so make them useful
  • Use verbs at the beginning of the title, such as "fix", "implement", "improve", "update", and "add"
  • Be specific about what was fixed or changed
  • Good Example: Fix the --should-snapshot-data CLI parameter to be preserved when the --data-output-directory property is not specified in the command.
  • Bad Example: Fixed --should-snapshot-data
• If there is an existing issue this addresses, include "Fixes #XXXX" to auto-link the issue to this PR
• If there is NOT an existing issue, consider creating one.
  • In general, issues describe wanted change from an end-user perspective and PRs describe the technical change.
  • If this change is very small and not worth splitting off an issue, include Steps To Reproduce, Expected Behavior, and Actual Behavior sections in this PR as you would have in the issue.
• Describe what users need and how the fix will affect them
• Describe how the code change addresses the problem
• Ensure private information is redacted.

Things to be aware of

• Describe the technical choices you made
• Describe impacts on the codebase

Things to worry about

• List any questions or concerns you have with the change
• List unknowns you have

Additional Context

Add any other context about the problem here.

[nvoxland]

These lines need to be fixed up

[github-actions]

Unit Test Results

  4 620 files  ±0    4 620 suites  ±0   33m 1s ⏱️ - 3m 19s
  4 611 tests ±0    4 396 ✔️ +4     215 💤  - 4  0 ❌ ±0 
54 504 runs  ±0  49 484 ✔️ +4  5 020 💤  - 4  0 ❌ ±0 

Results for commit 01940fb. ± Comparison against base commit 4215cf6.