Update CHANGELOG

Author: e10harvey

CHANGELOG.md

@@ -20,20 +20,25 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.4.0] <!-- YYYY-MM-DD --> [Unreleased]
 #### Added
 #### Changed
-- TODO: Add notes for !16/!17 // TRILFRAME-120 + TRILFRAME-136
 - Changes to `opt-set-cmake-var` behaviour:
   - Trigger a WARNING if `PARENT_SCOPE` and a _TYPE_ is provided since CMake
     requires TYPED vars to be CACHE vars and `PARENT_SCOPE` will force the
     var to be considered a non CACHE var that would store the parameters
-    before `PARENT_SCOPE` in the call as _list_ entries.
+    before `PARENT_SCOPE` in the call as _list_ entries. (TRILFRAME-128)
   - Trigger an exception if `PARENT_SCOPE` and `FORCE` are both provided since
     `FORCE` is only valid for CACHE variables but `PARENT_SCOPE` is only valid
     for non-CACHE vars (and as noted above will _force_ the `set()` operation
     to be a non-CACHE var which then triggers a CMake error because `FORCE` is
-    invalid to that form of `set()`.
+    invalid to that form of `set()`. (TRILFRAME-128)
   - **bash** generated options that have a TYPE and `PARENT_SCOPE` are processed
     to generate the same _list_ string that would be generated by the matching
-    `set()` operation (with the warning).
+    `set()` operation (with the warning). (TRILFRAME-128)
+  - For **bash** generation, trigger a WARNING and DO NOT generate the `-D` CLI option 
+    if `opt-set-cmake-var` without `FORCE` is called on a CMake Cache variable that has 
+    already been set. (TRILFRAME-120).
+  - For **bash** generation, trigger a WARNING and DO NOT generate the `-D` CLI option 
+    if `opt-set-cmake-var` is called on a non-cache CMake variable. (TRILFRAME-136)
+  - For **bash** generation, always add a _TYPE_ to the `-D` CLI option. (TRILFRAME-136)
 - Revert(ish) the modifications from MR12 which removed the error when generating
   BASH output if there is an unhandled CMake variable left hanging around.
   Rather than make this an unavoidable error though, ExpandVarsInText now inherits