Well, for release builds we want to build everything? #3817

## January 2022 Release - "Tin Can"

.github/workflows/build-firmware.yaml

@@ -195,7 +195,8 @@ jobs:
     steps:
     - name: Execution throttle early exit
       if: ${{ matrix.skip-rate }}
-      run: if (($(($RANDOM % 100)) < ${{ matrix.skip-rate }})); then echo "skip=true" >> $GITHUB_ENV; fi
+      # todo: how do we produce well-defined releases with skip-rate approach? For I can think of hacking the line below before a release
+      run: if (($(($RANDOM % 100)) < ${{ matrix.skip-rate }})); then echo "skip=not_true" >> $GITHUB_ENV; fi
 
     - uses: actions/checkout@v1
       if: ${{ env.skip != 'true' }}

firmware/CHANGELOG.md

@@ -25,7 +25,7 @@ Release template (copy/paste this for new release):
 
 All notable user-facing or behavior-altering changes will be documented in this file.
 
-## Month 202x Release - "Release Name"
+## January 2022 Release - "Tin Can"
 
 ### Added
  - Per-cylinder fuel trim tables